| 3 | Approval of the Agenda | |
|---|---|---|
| R3-224200 | RAN3#117-e Meeting Agenda | RAN3 Chair |
| 4 | Approval of the minutes from previous meetings | |
| R3-224201 | RAN3#116-e Meeting report | ETSI-MCC |
| 5 | Documents for immediate consideration | |
| R3-224230 | Guidelines for RAN3 Electronic Meetings | RAN3 Chair, RAN3 Vice-Chairs |
| 7 | General, protocol principles and issues | |
| R3-224202 | TR 30.531 v1.43.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| R3-225047 | TR 30.531 v1.43.1 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| 8.1 | New Incoming LSs | |
| R3-224203 | Reply LS on NR QoE | CT1 |
| R3-224211 | LS on the maximum PTW length of IDLE eDRX | RAN2 |
| R3-224212 | Reply LS on NR satellite RAT type in UE NAS | RAN2 |
| R3-224215 | LS on questions on RAN visible QoE | RAN2 |
| R3-224219 | LS On FS_REDCAP_Ph2 option feasibility | SA2 |
| R3-224220 | LS reply on Reply LS on NTN specific User Consent and UE location in connected mode in NTN | SA3 |
| R3-224222 | LS Reply on QoE configuration and reporting related issues | SA5 |
| R3-224224 | Reply LS on configuration updates of MDT M1, M8 and M9 in RAN3 specifications | SA5 |
| R3-224243 | Draft reply LS on the maximum PTW length of IDLE eDRX | Qualcomm Incorporated |
| R3-224259 | Solution selection to support long eDRX | ZTE |
| R3-224260 | [Draft]reply LS on FS_REDCAP_Ph2 option feasibility | ZTE |
| R3-224310 | Reply LS on FS_REDCAP_Ph2 option feasibility | Qualcomm India Pvt Ltd |
| R3-224365 | [Draft] LS Reply to Questions on RAN Visible QoE | Ericsson |
| R3-224366 | (CR TS 38.300) Correction for QoE | Ericsson |
| R3-224367 | (CR TS 38.300) Correction for RVQoE | Ericsson |
| R3-224368 | (CR TS 38.473) Correction for RVQoE | Ericsson |
| R3-224554 | Correction of Paging eDRX Information | Nokia, Nokia Shanghai Bell |
| R3-224555 | Correction of Paging eDRX Information | Nokia, Nokia Shanghai Bell |
| R3-224556 | Correction of Paging eDRX Information | Nokia, Nokia Shanghai Bell |
| R3-224557 | Correction of Paging eDRX Information | Nokia, Nokia Shanghai Bell |
| R3-224559 | Answers to RAN2 on questions on RAN visible QoE | Nokia, Nokia Shanghai Bell |
| R3-224584 | Correction to RedCap PTW | Huawei |
| R3-224585 | Correction to RedCap PTW | Huawei |
| R3-224586 | Correction to RedCap PTW | Huawei |
| R3-224592 | [DRAFT] Relpy LS on the maximum PTW length of IDLE eDRX | Huawei |
| R3-224593 | Discussion on eDRX support for UE in RRC_INACTIVE state | Huawei |
| R3-224594 | [DRAFT] Relpy LS on FS_REDCAP_Ph2 option feasibility | Huawei |
| R3-224597 | [DRAFT] Relpy LS on QoE configuration and reporting related issues | Huawei |
| R3-224598 | Discussion on questions on RAN visible QoE | Huawei |
| R3-224599 | [DRAFT] Relpy LS on questions on RAN visible QoE | Huawei |
| R3-224721 | R17 Correction on maximum PTW length of IDLE eDRX to TS38.423 | ZTE |
| R3-224722 | R17 Correction on maximum PTW length of IDLE eDRX to TS38.473 | ZTE |
| R3-224723 | R17 Correction on maximum PTW length of IDLE eDRX to TS38.413 | ZTE |
| R3-224724 | [Draft] Reply LS on maximum PTW length of IDLE eDRX | ZTE |
| R3-224742 | Discussion on LS on FS_REDCAP_Ph2 option feasibility | CATT |
| R3-224800 | Propositions for RAN3 feedback to SA2 on Rel-18 RedCap enhancement study | Ericsson |
| R3-224801 | [Draft] Reply LS On FS_REDCAP_Ph2 TR option feasibility | Ericsson |
| R3-224812 | Correction of the maximum PTW length of IDLE eDRX | Ericsson |
| R3-224813 | Correction of the maximum PTW length of IDLE eDRX | Ericsson |
| R3-224814 | Correction of the maximum PTW length of IDLE eDRX | Ericsson |
| R3-224837 | Discussion on RAN visible QoE | Samsung |
| R3-224838 | Reply LS on RAN visible QoE | Samsung |
| R3-224959 | [draft] Reply LS on FS_REDCAP_Ph2 option feasibility | CATT |
| R3-224984 | CB: # 1_PTW_Length | Nokia - moderator |
| R3-224985 | CB: # 2_RVQoE - Summary of email discussion | Ericsson - moderator |
| R3-224986 | CB: # 3_R18Redcap - Summary of email discussion | ZTE - moderator |
| R3-225048 | CB: # 50_QoESA5LS - Summary of email discussion | Ericsson - moderator |
| R3-225062 | (CR TS 38.300) Correction for QoE | Ericsson, Samsung, Nokia, Nokia Shanghai Bell |
| R3-225081 | LS On UE capability signalling for IoT-NTN | RAN2 |
| R3-225091 | Correction of Paging eDRX Information | Nokia, Nokia Shanghai Bell, ZTE |
| R3-225108 | Correction of the maximum PTW length of IDLE eDRX | Ericsson, Huawei, Nokia, Nokia Shanghai bell, ZTE |
| R3-225109 | Correction to RedCap PTW | Huawei, Nokia, Nokia Shanghai bell, Ericsson |
| R3-225119 | Reply LS on FS_REDCAP_Ph2 option feasibility | ZTE |
| R3-225204 | CB: # 2_RVQoE - Summary of email discussion | Ericsson - moderator |
| R3-225218 | CB: # 2_RVQoE - Summary of email discussion | Ericsson - moderator |
| 9.1 | LTE | |
| R3-224676 | Introducing Report Amount for M4, M5, M6, M7 measurements for E-UTRAN | Huawei, Deutsche Telekom, Orange |
| R3-224677 | Introducing Report Amount for M4, M5, M6, M7 measurements for E-UTRAN | Huawei, Deutsche Telekom, Orange |
| R3-224678 | Introducing Report Amount for M4, M5, M6, M7 measurements for E-UTRAN | Huawei, Deutsche Telekom, Orange |
| R3-224804 | Addition of Masked IMEISV for UEs using CP CIoT EPS optimisation | Ericsson, Vodafone, Qualcomm Incorporate, AT&T, Nokia, Nokia Shanghai Bell |
| R3-224805 | Addition of Masked IMEISV for UEs using CP CIoT EPS optimisation | Ericsson, Vodafone, Qualcomm Incorporate, AT&T, Nokia, Nokia Shanghai Bell |
| R3-224806 | Addition of Masked IMEISV for UEs using CP CIoT EPS optimisation | Ericsson, Vodafone, Qualcomm Incorporate, AT&T, Nokia, Nokia Shanghai Bell |
| R3-224807 | Addition of Masked IMEISV for UEs using CP CIoT EPS optimisation | Ericsson, Vodafone, Qualcomm Incorporate, AT&T, Nokia, Nokia Shanghai Bell |
| R3-224808 | Addition of Masked IMEISV for UEs using CP CIoT EPS optimisation | Ericsson, Vodafone, Qualcomm Incorporate, AT&T, Nokia, Nokia Shanghai Bell |
| R3-224920 | Correction of LTE MDT on event trigger logging and Sensor information_S1AP | ZTE, Samsung, China Telecom, Ericsson,CATT |
| R3-224921 | Correction of LTE MDT on Sensor information_X2AP | ZTE, Samsung, China Telecom, Ericsson,CATT |
| R3-225049 | Addition of Masked IMEISV for UEs using CP CIoT EPS optimisation | Ericsson, Vodafone, Qualcomm Incorporate, AT&T, Nokia, Nokia Shanghai Bell |
| R3-225050 | Addition of Masked IMEISV for UEs using CP CIoT EPS optimisation | Ericsson, Vodafone, Qualcomm Incorporate, AT&T, Nokia, Nokia Shanghai Bell |
| R3-225051 | Addition of Masked IMEISV for UEs using CP CIoT EPS optimisation | Ericsson, Vodafone, Qualcomm Incorporate, AT&T, Nokia, Nokia Shanghai Bell |
| R3-225052 | Addition of Masked IMEISV for UEs using CP CIoT EPS optimisation | Ericsson, Vodafone, Qualcomm Incorporate, AT&T, Nokia, Nokia Shanghai Bell |
| R3-225274 | Correction of LTE MDT on Sensor information[LTE-Height-MDT] | ZTE, Samsung, China Telecom, Ericsson, CATT, NEC |
| R3-225280 | Correction of LTE MDT on Sensor information[LTE-Height-MDT] | ZTE, Samsung, China Telecom, Ericsson, CATT, NEC |
| 9.2.1 | User Consent for Trace | |
| R3-224242 | On the handling of user consent for RLF/CEF cases | Nokia, Nokia Shanghai Bell |
| R3-224400 | Resolution of the issue of user consent for location in RLF/CEF | Apple |
| R3-224401 | User consent for location information in RLF/CEF – option 1 (TS 38.413) | Apple |
| R3-224402 | User consent for location information in RLF/CEF – option 1 (TS 38.423) | Apple |
| R3-224403 | User consent for location information in RLF/CEF – option 2 (TS 38.413) | Apple |
| R3-224404 | User consent for location information in RLF/CEF – option 2 (TS 38.423) | Apple |
| R3-224405 | [DRAFT] Reply LS on the user consent for trace reporting | Apple |
| R3-224573 | Way forward on user consent | Ericsson, TIM |
| R3-224679 | Discussion on user consent for UE location information (CRs and draft reply LS included) | Huawei, Orange |
| R3-224987 | CB: # 4_UserConsent - Summary of email discussion | Nokia - moderator |
| R3-225037 | Way forward on user consent | Ericsson, TIM, Apple |
| R3-225194 | [Draft] Reply LS on the user consent for trace reporting | Nokia |
| R3-225239 | [Draft] Reply LS on the user consent for trace reporting | Nokia |
| R3-225250 | Reply LS on the user consent for trace reporting | Nokia |
| 9.2.2 | Flexible gNB ID | |
| R3-224213 | Reply LS on Flexible Global RAN Node ID | RAN2 |
| R3-224569 | [DRAFT] Reply LS on Flexible Global RAN Node ID | Ericsson |
| R3-224680 | Support for flexible gNB ID length [FLEX_gNB_Len] | Huawei, Qualcomm Incorporated, Ericsson |
| R3-224988 | CB: # 5_Flexible_gNBID - Summary of email discussion | Ericsson - moderator |
| R3-225125 | Support for flexible gNB ID length [FLEX_gNB_Len] | Huawei, Qualcomm Incorporated, Ericsson |
| R3-225157 | [DRAFT] Reply LS on Flexible Global RAN Node ID | Ericsson |
| R3-225205 | Support for flexible gNB ID length [FLEX_gNB_Len] | Huawei, Qualcomm Incorporated, Ericsson |
| R3-225228 | Support for flexible gNB ID length [gNB_ID_Length] | Huawei, Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-225248 | Reply LS on Flexible Global RAN Node ID | Ericsson |
| 9.2.3 | Resource Coordination between LTE and NR | |
| R3-224466 | Resource Coordination between LTE and NR | Nokia, Nokia Shanghai Bell |
| R3-224480 | Resource Coordination between SA gNB and LTE eNB | China Telecom |
| R3-224481 | LS on the support of only resource coordination in NCR | China Telecom |
| R3-224980 | Resource Coordination between SA gNB and LTE eNB | China Telecom,ZTE,Huawei |
| R3-224981 | Introduction of new attributes “Only Resource Coordination” in ANR | Ericsson, China Telecom, CATT |
| R3-224989 | CB: # 6_Resource_Coordination - Summary of email discussion | China Telecom - moderator |
| R3-225038 | Introduction of new attributes “Only Resource Coordination” in ANR | Ericsson, China Telecom, CATT, Huawei |
| R3-225158 | Introduction of new attributes “Only Resource Coordination” in ANR | Ericsson, China Telecom, CATT, Huawei, ZTE |
| R3-225160 | LS on the support of only resource coordination in NCR | China Telecom |
| R3-225206 | LS on introduction of a new attribute “Only Resource Coordination” to support source coordination between LTE and NR SA | China Telecom |
| 9.2.4 | SONMDT | |
| R3-224223 | LS on Reply LS on beam measurement reports | SA5 |
| R3-224225 | LS on changes over E1AP due to RACH NSA Measurements | SA5 |
| R3-224250 | Completion of the missing descripition of SCG MRO handling | Nokia, Nokia Shanghai Bell |
| R3-224272 | Correction of Inter-system Resource Status Reporting | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE |
| R3-224273 | ASN.1 correction for Inter-system Resource Status Report | Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-224441 | Correction of the wrong constant definition in ASN.1 | Nokia, Nokia Shanghai Bell |
| R3-224486 | Discussion on enabling further Beam level measurement report configurations in M1 in support of SA5 requests | Ericsson |
| R3-224487 | (draft) Reply LS on beam measurement reports | Ericsson |
| R3-224536 | SHR correction | Huawei, Deutsche Telekom, Qualcomm, CMCC |
| R3-224537 | SHR correction | Huawei, Deutsche Telekom, Qualcomm, CMCC |
| R3-224538 | SHR correction | Huawei, Deutsche Telekom, Qualcomm, CMCC |
| R3-224539 | SHR correction | Huawei, Deutsche Telekom, Qualcomm, CMCC |
| R3-224540 | MR-DC UHI correction | Huawei, Deutsche Telekom, Qualcomm, Vodafone, Orange, CMCC |
| R3-224541 | MR-DC UHI correction | Huawei, Deutsche Telekom, Qualcomm, Vodafone, Orange, CMCC |
| R3-224542 | MR-DC UHI correction | Huawei, Deutsche Telekom, Qualcomm, Vodafone, Orange, CMCC |
| R3-224543 | MR-DC UHI correction | Huawei, Deutsche Telekom, Qualcomm, Vodafone, Orange, CMCC |
| R3-224558 | UE History Information correlation | Ericsson |
| R3-224681 | Discussion on Excess Packet delay (CRs included) | Huawei |
| R3-224682 | Discussion on early measurement collection (CRs included) | Huawei |
| R3-224683 | Discussion on remaining issues for NR-U MLB (CRs included) | Huawei |
| R3-224684 | Discussion on reply LS on beam measurement reports (CRs included) | Huawei |
| R3-224816 | UE History Information for CHO and MR-DC | Samsung, Verizon, CATT |
| R3-224817 | Correction of UE History Information for CHO and MR-DC | Samsung, Verizon, CATT |
| R3-224818 | Correction of UE History Information for CHO and MR-DC | Samsung, Verizon, CATT |
| R3-224819 | CCO Issue Detection over Xn | Samsung, Verizon |
| R3-224820 | The inclusion of the CCO Issue Detection over Xn signalling | Samsung, Verizon |
| R3-224844 | Discussion on SON for NR-U to support DL MLB | Samsung |
| R3-224845 | Correction of NR-U information exchange for DL MLB | Samsung |
| R3-224846 | Correction of NR-U information exchange for DL MLB | Samsung |
| R3-224883 | Correction on Rel-17 SON stage 2 | ZTE |
| R3-224930 | Corrections related to Excess Packet Delay | Ericsson |
| R3-224932 | Additional SON consideration for Mobility Enhancements features | Ericsson |
| R3-224950 | Correction to Report Caracteristics | Ericsson, Deutsche Telekom, ZTE, CATT, China Telecom, CMCC. China Unicom |
| R3-224951 | Correction to Report Caracteristics | Ericsson, Deutsche Telekom, ZTE, CATT, China Telecom, CMCC, China Unicom |
| R3-224972 | Discussion on corrections for UE History Information in MR-DC | ZTE, Lenovo, China Unicom |
| R3-224973 | Correction for TS 38.413 on UHI in MR-DC | ZTE, Lenovo, China Unicom |
| R3-224974 | Correction for TS 36.413 on UHI in MR-DC | ZTE, Lenovo |
| R3-224975 | Correction for TS 38.300 on UHI in MR-DC | ZTE, Lenovo, China Unicom |
| R3-224976 | Correction for TS 38.423 on UHI in MR-DC | ZTE, Lenovo, China Unicom |
| R3-224977 | Correction for TS 36.423 on UHI in MR-DC | ZTE, Lenovo, China Unicom |
| R3-224990 | CB: # 7_UHI - Summary of email discussion | ZTE - moderator |
| R3-224991 | CB: # 8_R17SONMDT_Others - Summary of email discussion | Huawei - moderator |
| R3-225133 | The inclusion of the CCO Issue Detection over Xn signalling | Samsung, Verizon, Ericsson |
| R3-225137 | Correction on excess packet delay | Huawei |
| R3-225138 | Correction on excess packet delay | Huawei |
| R3-225139 | Correction for TS 38.423 on UHI in MR-DC | ZTE, Lenovo, China Unicom |
| R3-225140 | Correction for TS 36.423 on UHI in MR-DC | ZTE, Lenovo, China Unicom |
| R3-225142 | Correction on NR-U MLB | Huawei, Ericsson |
| R3-225143 | Correction on NR-U MLB | Huawei, Ericsson |
| R3-225144 | Correction to early measurement collection | Huawei, Ericsson |
| R3-225145 | Correction to early measurement collection | Huawei, Ericsson |
| R3-225147 | Collection on beam measurement report configuration in M1 | Huawei, Ericsson |
| R3-225148 | Collection on beam measurement report configuration in M1 | Huawei, Ericsson |
| R3-225151 | Correction of Inter-system Resource Status Reporting | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE |
| R3-225159 | Reply LS on beam measurement reports | Ericsson |
| R3-225190 | Completion of the missing descripition of SCG MRO handling | Nokia, Nokia Shanghai Bell, ZTE |
| R3-225191 | Correction of the wrong constant definition in ASN.1 | Nokia, Nokia Shanghai Bell |
| R3-225200 | NGAP Corrections related to Excess Packet Delay | Ericsson, Huawei |
| R3-225201 | XnAP Corrections related to Excess Packet Delay | Ericsson, Huawei |
| R3-225222 | Correction for TS 38.300 on UHI in MR-DC | ZTE, Lenovo, China Unicom |
| R3-225244 | Clarification of PSCell ID handling for SCG MRO handling | Nokia, Nokia Shanghai Bell |
| R3-225258 | Collection on beam measurement report configuration in M1 | Huawei, Ericsson |
| R3-225259 | Collection on beam measurement report configuration in M1 | Huawei, Ericsson |
| R3-225260 | Correction on NR-U MLB | Huawei, Ericsson |
| R3-225261 | Correction on NR-U MLB | Huawei, Ericsson |
| R3-225262 | Correction to early measurement collection | Huawei, Ericsson |
| R3-225273 | Reply LS on beam measurement reports | Ericsson |
| R3-225275 | Correction to Report Caracteristics | Ericsson, Deutsche Telekom, ZTE, CATT, China Telecom, CMCC, China Unicom |
| 9.2.5 | IAB | |
| R3-224209 | LS on upper layers parameters for Rel-17 eIAB | RAN1 |
| R3-224236 | CR for 38.473 on Rel-17 IAB enhancements to topology adapatation | Qualcomm Inc. |
| R3-224349 | Correction on IAB Multiplexing info | Huawei, Lenovo, Ericsson, Samsung |
| R3-224350 | Miscellaneous Correction on IAB | Huawei, Qualcomm, Ericsson |
| R3-224351 | Miscellaneous Correction on IAB | Huawei, Qualcomm, Lenovo, Fujitsu, Ericsson |
| R3-224352 | Correction on protocol stack for IAB | Huawei, Qualcomm, Lenovo, Fujitsu, Ericsson |
| R3-224500 | (CR TS 38.423) Correction to RB Set Definition | Ericsson |
| R3-224501 | (CR TS 38.473) Correction to RB Set Definition | Ericsson |
| R3-224503 | CR for 38.473 on Rel-17 IAB enhancements to topology adapatation | Qualcomm Inc. |
| R3-224703 | Corrections on IAB inter-CU topology adaptation | Fujitsu |
| R3-224715 | Miscellaneous corrections on IAB in TS 38.473 | ZTE |
| R3-224735 | Correction to 38.420 for IAB | CATT |
| R3-224992 | CB: # 9_R17IAB - Summary of email discussion | Qualcomm - moderator |
| R3-225042 | (CR TS 38.423) Correction to RB Set Definition | Ericsson |
| R3-225043 | (CR TS 38.473) Correction to RB Set Definition | Ericsson |
| R3-225044 | CR for 38.473 on Rel-17 IAB enhancements to topology adapatation | Qualcomm Inc. |
| R3-225136 | Miscellaneous Correction on IAB | Huawei, Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-225175 | Corrections on IAB inter-CU topology adaptation | Fujitsu |
| R3-225186 | Miscellaneous corrections on IAB in TS 38.473 | ZTE |
| R3-225198 | Correction to 38.420 for IAB | CATT |
| R3-225209 | CR for 38.473 on Rel-17 IAB enhancements to topology adapatation | Qualcomm Inc. |
| R3-225249 | CB: # 9_R17IAB - Summary of email discussion | Qualcomm - moderator |
| R3-225263 | Corrections on IAB inter-CU topology adaptation | Fujitsu |
| 9.2.6 | Positioning | |
| R3-224205 | Reply LS on the UE/TRP TEG framework | RAN1 |
| R3-224206 | LS on updates of RRC parameters for Rel-17 positioning enhancements | RAN1 |
| R3-224207 | LS reply on questions concerning the implementation of RAN1 agreements in NRPPa | RAN1 |
| R3-224208 | Reply LS on expected AoA and AoD parameters | RAN1 |
| R3-224210 | LS on expected AoA and AoD parameters | RAN2 |
| R3-224214 | LS to RAN3 on container for SRS configuration for positioning | RAN2 |
| R3-224216 | LS on Tx TEG framework | RAN4 |
| R3-224274 | Correction for UE Tx TEG Association | Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei, Samsung |
| R3-224338 | Introduction of SRS port index | Huawei, Ericsson, CATT |
| R3-224525 | Addition of SRS port index | Ericsson, Huawei, CATT |
| R3-224638 | Support of timing error margins for TEG in NRPPa | CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung |
| R3-224639 | Support of timing error margins for TEG in F1AP | CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung |
| R3-224640 | Draft Reply LS on Tx TEG framework | CATT |
| R3-224685 | CR to 38.470 on UE context management function | Huawei, China Unicom, CMCC |
| R3-224686 | CR to 38.455 on E-CID measurement periodicity | Huawei, China Unicom, CMCC |
| R3-224687 | CR to 38.455 on E-CID measurement periodicity | Huawei, China Unicom, CMCC |
| R3-224688 | CR to 38.473 on E-CID measurement periodicity | Huawei, China Unicom, CMCC |
| R3-224689 | CR to 38.473 on E-CID measurement periodicity | Huawei, China Unicom, CMCC |
| R3-224690 | Discussion on remaining issues for positioning | Huawei |
| R3-224691 | CR to 38.455 on miscellaneous corrections | Huawei |
| R3-224692 | Correction on cause value for positioning | Huawei |
| R3-224693 | CR to 38.455 on SRS periodicity | Huawei, China Unicom, CMCC |
| R3-224694 | CR to 38.455 on SRS periodicity | Huawei, China Unicom, CMCC |
| R3-224695 | CR to 38.473 on SRS periodicity | Huawei, China Unicom, CMCC |
| R3-224696 | CR to 38.473 on SRS periodicity | Huawei, China Unicom, CMCC |
| R3-224782 | Support and way forward for SRS-PosRRC-InactiveConfig-r17 configuration in a CU-DU split architecture | Intel Corporation |
| R3-224783 | Rel-17 ePos correction for the missing support of SRS-PosRRC-InactiveConfig-r17 configuration | Intel Corporation |
| R3-224784 | [Draft] LS on SRS-PosRRC-InactiveConfig configuration signalling | Intel Corporation |
| R3-224798 | CR to 38.455 to addition of TRP TEG timing error margins | ZTE |
| R3-224809 | Correction of PPW/MG procedures | Ericsson |
| R3-224810 | Support of PPW pre-configuration continuity during Xn mobility | Ericsson |
| R3-224811 | Correction to the PRS Measurement configuration procedures | Ericsson |
| R3-224870 | Positioning SRS configuration transfer for RRC inactive and other aspects in LSs | Huawei, CMCC, China Unicom |
| R3-224871 | Positioning SRS configuration transfer for RRC inactive | Huawei, CMCC, China Unicom |
| R3-224935 | Correction to positioning gap configuration – alt. 1 | Google Inc. |
| R3-224941 | Correction to positioning gap configuration – alt. 2 | Google Inc. |
| R3-224971 | Correction on cause value for positioning | Huawei |
| R3-224993 | CB: # 18_R17Positioning_Corr - Summary of email discussion | CATT - moderator |
| R3-224994 | CB: # 19_R17Positioning_Inactive_PPW - Summary of email discussion | Ericsson - moderator |
| R3-225005 | Response to R3-224782 | Beijing Xiaomi Mobile Software |
| R3-225126 | CR to 38.455 on miscellaneous corrections | Huawei |
| R3-225127 | CR to 38.455 on E-CID measurement periodicity | Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-225128 | CR to 38.455 on E-CID measurement periodicity | Huawei, China Unicom, CMCC |
| R3-225129 | CR to 38.473 on E-CID measurement periodicity | Huawei, China Unicom, CMCC |
| R3-225130 | CR to 38.473 on E-CID measurement periodicity | Huawei, China Unicom, CMCC |
| R3-225131 | Correction on Measurement Time Occasion | Huawei |
| R3-225132 | Correction to positioning gap configuration | Google Inc. |
| R3-225152 | Correction for UE Tx TEG Association | Nokia, Nokia Shanghai Bell, CATT, Ericsson, Huawei, Samsung |
| R3-225187 | Support of timing error margins for TEG in NRPPa | CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung |
| R3-225188 | Support of timing error margins for TEG in F1AP | CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung |
| R3-225195 | Draft reply LS on Tx TEG framework | Ericsson |
| R3-225208 | Correction to positioning gap configuration | Google Inc. |
| R3-225210 | CB: # 18_R17Positioning_Corr - Summary of email discussion | CATT - moderator |
| R3-225213 | Rel-17 ePos correction for the missing support of SRS-PosRRC-InactiveConfig-r17 configuration | Intel Corporation, Ericsson, Xiaomi, Google |
| R3-225214 | (Draft) LS on SRS-PosRRC-InactiveConfig configuration signalling | Intel Corporation |
| R3-225223 | Support of timing error margins for TEG in NRPPa | CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-225224 | Support of timing error margins for TEG in F1AP | CATT, Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-225264 | CR to 38.455 on E-CID measurement periodicity | Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-225265 | CR to 38.455 on E-CID measurement periodicity | Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-225266 | CR to 38.473 on E-CID measurement periodicity | Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell,CATT |
| R3-225267 | CR to 38.473 on E-CID measurement periodicity | Huawei, China Unicom, CMCC, Ericsson, Nokia, Nokia Shanghai Bell, CATT |
| R3-225268 | LS on SRS-PosRRC-InactiveConfig configuration signalling | Intel Corporation |
| 9.2.7 | MBS | |
| R3-224204 | LS on Support of Broadcast and Multicast MBS sessions with AMF Set | CT4 |
| R3-224221 | Reply LS on the MBS broadcast service continuity and MBS session identification | SA4 |
| R3-224327 | Consideration on Multicast Data Forwarding and F1-U Tunnel aspects | Huawei, CBN, China Unicom, Nokia, Nokia Shanghai Bell |
| R3-224328 | Multicast Data Forwarding and F1-U tunnel aspects | Huawei, CBN, China Unicom, Nokia, Nokia Shanghai Bell |
| R3-224329 | Multicast Data Forwarding and F1-U tunnel aspects | Huawei, CBN, China Unicom, Nokia, Nokia Shanghai Bell |
| R3-224330 | Other leftover issues on NGAP for MBS | Huawei, CBN, Qualcomm Incorporated |
| R3-224331 | Correction on other leftover issues on NGAP for MBS | Huawei, CBN, Qualcomm Incorporated |
| R3-224332 | Other leftover issues on F1 and E1 for MBS | Huawei, CBN, Qualcomm Incorporated, Lenovo |
| R3-224333 | Correction on Broadcast and Unicast co-existence | Huawei, CBN, Qualcomm Incorporated, CATT, Lenovo |
| R3-224334 | Correction on Multicast Session Establishment | Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, CATT, Lenovo |
| R3-224406 | F1-U tunnels related issues | Lenovo |
| R3-224407 | Correction on F1-U tunnels for multicast MRB | Lenovo |
| R3-224408 | Correction on F1-U tunnels for multicast MRB | Lenovo |
| R3-224409 | Correction on User Inactivity for Multicast Session | Lenovo |
| R3-224442 | Correction of address management for shared CU UP | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Orange |
| R3-224443 | Correction of address management for shared CU UP | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Orange |
| R3-224444 | Correction of address management for shared CU UP | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Orange |
| R3-224445 | Correction of MBS broadcast release required | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Lenovo, Huawei |
| R3-224446 | Correction of MBS broadcast release required | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Lenovo, Huawei |
| R3-224447 | Correction of shared CU UP codepoints | Nokia, Nokia Shanghai Bell, Ericsson, Orange |
| R3-224448 | Correction of shared CU UP codepoints | Nokia, Nokia Shanghai Bell, Ericsson, Orange |
| R3-224449 | Correction of MBS data forwarding | Nokia, Nokia Shanghai Bell, Huawei, Orange |
| R3-224450 | Correction of MBS data forwarding | Nokia, Nokia Shanghai Bell, Huawei, Orange |
| R3-224451 | Correction of stage 2 MBS | Nokia, Nokia Shanghai Bell |
| R3-224467 | General open issues - discussion | Ericsson, Qualcomm, Verizon Wireless, AT&T, China Unicom |
| R3-224468 | Further Corrections for NR MBS | Ericsson, Qualcomm, Verizon Wireless, AT&T, China Unicom |
| R3-224469 | Further Corrections for NR MBS | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Verizon Wireless, AT&T, China Unicom |
| R3-224470 | Further Corrections for NR MBS | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Verizon Wireless, AT&T, China Unicom |
| R3-224471 | Further Corrections for NR MBS | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Verizon Wireless, AT&T, China Unicom |
| R3-224472 | Further Corrections for NR MBS | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Verizon Wireless, AT&T, China Unicom |
| R3-224473 | Corrections for MBS-associated signalling | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, CATT, Verizon Wireless, AT&T, China Unicom |
| R3-224474 | Corrections for MBS-associated signalling | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, CATT, Verizon Wireless, AT&T, China Unicom |
| R3-224475 | Corrections for ptp retransmission topics and overall example message flow restructuring | Ericsson, Verizon Wireless, AT&T, China Unicom |
| R3-224476 | Corrections for the establishment of F1-U ptp retransmission tunnels | Ericsson, Verizon Wireless, AT&T, China Unicom |
| R3-224477 | Corrections to the example message flow for multicast MBS Context establishmen | Ericsson, Verizon Wireless, AT&T, China Unicom |
| R3-224478 | [Draft] Response LS on Support of Broadcast and Multicast MBS sessions with AMF Set | Ericsson |
| R3-224534 | Correction of MBS multicast HFN SN initialisation | Nokia, Nokia Shanghai Bell |
| R3-224535 | Correction of MBS multicast HFN SN initialisation | Nokia, Nokia Shanghai Bell |
| R3-224644 | E1AP ASN.1 correction on MCBearerContextToModify | CATT, Nokia, Nokia Shanghai Bell, Huawei, ZTE, Ericsson, Samsung, Lenovo |
| R3-224645 | Introduction of ongoing broadcast service in XnAP | CATT,Nokia, Nokia Shanghai Bell |
| R3-224646 | Introduction of abnormal handling for Multicast session deactivation | CATT |
| R3-224647 | Discussion on three issues on E1AP | CATT |
| R3-224648 | Correction on three issues on TS 37.483 | CATT |
| R3-224665 | Introduction of MBS specific cause values | Huawei, CBN, Qualcomm Incorporated |
| R3-224666 | Introduction of MBS specific cause values | Huawei, CBN, Qualcomm Incorporated |
| R3-224667 | Introduction of MBS specific cause values | Huawei, CBN, Qualcomm Incorporated |
| R3-224668 | Introduction of MBS specific cause values | Huawei, CBN, Qualcomm Incorporated |
| R3-224669 | Correction on Multicast Group Paging | Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo |
| R3-224670 | Correction on Multicast Group Paging | Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo |
| R3-224671 | Correction on Multicast Group Paging | Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo |
| R3-224672 | Multicast MRB ID change over F1 and E1 interfaces | Huawei, CBN, Qualcomm Incorporated, Lenovo |
| R3-224673 | Correction on MRB ID Change | Huawei, CBN, Qualcomm Incorporated, Lenovo |
| R3-224674 | Correction on MRB ID Change | Huawei, CBN, Qualcomm Incorporated, Lenovo |
| R3-224859 | Discussion for the MBS open issues | Samsung |
| R3-224860 | Correction for the MBS multicast data forwarding | Samsung |
| R3-224861 | Correction for the MRB progress information | Samsung |
| R3-224919 | Discussion on Multicast MBS Session Context Establishment | Google Inc. |
| R3-224933 | Clarification to Multicast MBS Session Context Establishment | Google Inc. |
| R3-224942 | Issues found in Rel-17 NR MBS with discussions and draft CR to F1AP | ZTE |
| R3-224943 | Correction to 38.401 on admission control of multicast session for NR MBS | ZTE, CMCC, Lenovo |
| R3-224944 | Correction to NGAP on distribution modification for NR MBS | ZTE, CMCC, Lenovo |
| R3-224995 | CB: # 20_R17MBS_GeneralandNG - Summary of email discussion | Huawei - moderator |
| R3-224996 | CB: # 21_R17MBS_XnF1E1 - Summary of email discussion | Ericsson - moderator |
| R3-225040 | Correction to 38.401 on admission control of multicast session for NR MBS | ZTE, CMCC, Lenovo |
| R3-225041 | Correction to NGAP on distribution modification for NR MBS | ZTE, CMCC, Lenovo |
| R3-225094 | Correction of stage 2 MBS | Nokia, Nokia Shanghai Bell |
| R3-225124 | Draft LS on Shared N3 setup towards shared CU UP node | Nokia, Nokia Shanghai Bell |
| R3-225155 | Correction of shared CU UP codepoints | Nokia, Nokia Shanghai Bell, Ericsson, Orange |
| R3-225164 | Further Corrections for NR MBS | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Verizon Wireless, AT&T, China Unicom, ZTE |
| R3-225165 | Response LS on Support of Broadcast and Multicast MBS sessions with AMF Set | Ericsson |
| R3-225166 | Corrections for the establishment of F1-U ptp retransmission tunnels | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Verizon Wireless, AT&T, China Unicom, ZTE |
| R3-225167 | Further Corrections for NR MBS | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Verizon Wireless, AT&T, China Unicom, ZTE |
| R3-225168 | Further Corrections for NR MBS | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Verizon Wireless, AT&T, China Unicom, ZTE |
| R3-225169 | Corrections for the establishment of F1-U ptp retransmission tunnels | Ericsson, Verizon Wireless, AT&T, China Unicom, Nokia, Nokia Shanghai Bell, ZTE |
| R3-225170 | Correction for the MBS multicast data forwarding | Samsung, CATT, Huawei, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo |
| R3-225171 | Introduction of MBS specific cause values | Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-225172 | Introduction of MBS specific cause values | Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-225173 | Correction on MRB ID Change | Huawei, CBN, Qualcomm Incorporated, Lenovo, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-225174 | Correction on Maximum number or MRB IDs | Huawei, CBN, Qualcomm Incorporated, Lenovo, Nokia, Nokia Shanghai Bell, ZTE |
| R3-225176 | Correction on Multicast Group Paging | Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Google |
| R3-225177 | Correction on Multicast Group Paging | Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo, ZTE, Google |
| R3-225178 | Correction on Multicast session deactivation procedure | CATT, Nokia, Nokia Shanghai Bell |
| R3-225179 | Introduction of MBS specific cause values | Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-225180 | Correction on other leftover issues on NGAP for MBS | Huawei, CBN, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, ZTE |
| R3-225230 | Corrections for the establishment of F1-U ptp retransmission tunnels | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm, Verizon Wireless, AT&T, China Unicom, ZTE, Samsung, Huaweil |
| R3-225231 | CB: # 21_R17MBS_XnF1E1 - Summary of email discussion | Ericsson - moderator |
| R3-225245 | Corrections for the establishment of F1-U ptp retransmission tunnels | Ericsson, Verizon Wireless, AT&T, China Unicom, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-225246 | Correction for the MBS multicast data forwarding | Samsung, CATT, Huawei, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo, Huawei |
| R3-225247 | LS on shared NG-U Termination among gNBs | Nokia, Nokia Shanghai Bell |
| 9.2.8 | Others | |
| R3-224217 | LS on timing advance (TADV) report mapping for NR UL E-CID positioning | RAN4 |
| R3-224246 | Correction of the desctiption of the transport bearer address to enable direct data transfer in DC operation | Nokia, Nokia Shanghai Bell, CATT, ZTE, Samsung, Deutsche Telekom |
| R3-224247 | Clarification of the desired buffer size in case of retransmissions [DesBufRetrans] | Nokia, Nokia Shanghai Bell |
| R3-224248 | Coordination of CHO and intra-SN CPC | Nokia, Nokia Shanghai Bell, ZTE, Huawei, Ericsson |
| R3-224249 | Data forwarding in CPAC (incl. draft CRs) | Nokia, Nokia Shanghai Bell |
| R3-224261 | Completion of DAPS in case of split gNB deployment | ZTE |
| R3-224262 | Completion of DAPS in case of split gNB deployment to 38.473 | ZTE |
| R3-224263 | Completion of DAPS in case of split gNB deployment to 38.473 | ZTE |
| R3-224264 | Discussion on direct data forwarding for MN initiated CPC | ZTE, Lenovo, CATT, Huawei |
| R3-224265 | Clarification on direct data forwarding for MN initiated CPC to TS37340 | ZTE, Lenovo, CATT, Huawei |
| R3-224266 | Clarification on direct data forwarding for SN initiated CPC to TS37.340 | ZTE, Huawei, CATT |
| R3-224267 | Stage 2 Clarification on SDT to TS 38.401 | ZTE, China Telecom, CATT, Nokia, Nokia Shanghai Bell,Samsung |
| R3-224268 | Coordination of CHO and intra-SN CPC for TS37.340 | ZTE, Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-224275 | Correction of Slice Group Configuration | ZTE, Huawei, CMCC |
| R3-224276 | Discussion on coordination of CHO and intra-SN CPC | Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Huawei |
| R3-224282 | CAG access control without mobility restrictions | Huawei, Nokia, Nokia Shanghai Bell, Orange, Deutsche Telekom |
| R3-224283 | CAG access control without mobility restrictions | Huawei, Nokia, Nokia Shanghai Bell, Orange, Deutsche Telekom |
| R3-224284 | CAG access control without mobility restrictions | Huawei, Nokia, Nokia Shanghai Bell, Orange, Deutsche Telekom |
| R3-224285 | CAG access control without mobility restrictions | Huawei, Nokia, Nokia Shanghai Bell, Orange, Deutsche Telekom |
| R3-224288 | Correction of PRACH optimization | NEC |
| R3-224289 | Handling of PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE |
| R3-224290 | Handling of PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE, Huawei, CATT |
| R3-224291 | Handling of PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE, Huawei, CATT |
| R3-224292 | PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE |
| R3-224293 | PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE |
| R3-224294 | Indication of RedCap-specific NCD-SSB over Xn IF | NEC |
| R3-224295 | Correction for RedCap-specific NCD-SSB information exchange over Xn IF | NEC |
| R3-224309 | UE Capability for eMTC NTN to TN HO | Qualcomm India Pvt Ltd |
| R3-224311 | Direct or indirect early data forwarding in SN initiated inter-SN CPC | Huawei, Deutsche Telekom, ZTE, CATT |
| R3-224312 | Direct early data forwarding in SN initiated inter-SN CPC | Huawei, Deutsche Telekom, ZTE, CATT |
| R3-224313 | Direct early data forwarding in SN initiated inter-SN CPC | Huawei, Deutsche Telekom, ZTE, CATT |
| R3-224314 | Correction on gNB-DU ID | Huawei, Deutsche Telekom, China Unicom |
| R3-224315 | Correction on gNB-DU ID | Huawei, Deutsche Telekom, China Unicom |
| R3-224316 | Correction on gNB-DU ID | Huawei, Deutsche Telekom, China Unicom |
| R3-224317 | Correction on Missing Criticality Diagnostics over E1AP | Huawei, BT, Deutsche Telekom, Orange |
| R3-224318 | Correction on Missing Criticality Diagnostics over E1AP | Huawei, BT, Deutsche Telekom, Orange |
| R3-224319 | Correction on Missing Criticality Diagnostics over E1AP | Huawei, BT, Deutsche Telekom, Orange |
| R3-224320 | Coordination of CHO and intra-SN CPC | Huawei, Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-224321 | Discarding of the forwarded PDCP PDU in early data forwarding | Huawei |
| R3-224335 | Correction to SDT for supporting delta signaling | Google Inc., Huawei |
| R3-224336 | Correction to SDT for supporting delta signalling (option2) | Google Inc., Huawei |
| R3-224337 | Clarification to CG based SDT | Google Inc., Huawei |
| R3-224339 | Timer handling for CHO with SCG configuration [CHOwithDCkept] | Google Inc. |
| R3-224340 | Timer handling for CHO with SCG configuration [CHOwithDCkept] | Google Inc. |
| R3-224346 | CAG Access Control without mobility restriction | Nokia, Nokia Shanghai Bell, Huawei, Deutsche Telekom, Orange |
| R3-224347 | CAG Access Control without mobility restricition | Nokia, Nokia Shanghai Bell, Deutsche Telekom, Orange |
| R3-224374 | Update for Rel-17 NGAP IEs not applicable to non-3GPP access | Nokia, Nokia Shanghai Bell, Huawei, BT |
| R3-224389 | Addition of a CHO-related notes to a chapter on HO with DC [CHOwithDCkept] | Nokia, Nokia Shanghai Bell |
| R3-224452 | Correction of Xn data forwarding | Nokia, Nokia Shanghai Bell, Orange, Deutsche Telekom, China Telecom, CATT, Huawei |
| R3-224453 | Correction of Xn data forwarding | Nokia, Nokia Shanghai Bell, Orange, Deutsche Telekom, China Telecom, CATT, Huawei |
| R3-224454 | Correction of Xn data forwarding | Nokia, Nokia Shanghai Bell, Orange, Deutsche Telekom, China Telecom, CATT, Huawei |
| R3-224455 | Correction of Slice Group Configuration over Xn | Nokia, Nokia Shanghai Bell, CATT, NEC, LG Electronics |
| R3-224456 | Correction of Slice Group Configuration over Xn | Nokia, Nokia Shanghai Bell, CATT, NEC, LG Electronics |
| R3-224482 | RAN3 impacts for Extending NR Operation to 71GHz | China Telecom |
| R3-224483 | R17 CR for TS36.423 on Extending NR Operation to 71GHz | China Telecom |
| R3-224484 | R17 CR for TS38.423 on Extending NR Operation to 71GHz | China Telecom |
| R3-224485 | R17 CR for TS38.473 on Extending NR Operation to 71GHz | China Telecom |
| R3-224510 | CHO with SCG configuration | Qualcomm Incorporated |
| R3-224515 | Handling interaction between CPC cancel and SN release | Ericsson, Lenovo, ZTE |
| R3-224516 | Interaction between CPC Cancel and SN Release | Ericsson, Lenovo, ZTE |
| R3-224527 | Clarification on F1 Paging function | Ericsson, Huawei, ZTE, Qualcomm Inc. |
| R3-224544 | SL relay corrections | Huawei, Nokia, Nokia Shanghai Bell, China Unicom |
| R3-224545 | SL relay corrections | Huawei, Nokia, Nokia Shanghai Bell, China Unicom |
| R3-224546 | SL relay corrections | Huawei, Nokia, Nokia Shanghai Bell, China Unicom |
| R3-224570 | Corrections and way forward to Inter Frequency Measurements without Gaps | Ericsson, Qualcomm, Intel Corporation |
| R3-224571 | interFrequencyConfig-NoGap signaling from gNB-CU to gNB-DU | Ericsson, Qualcomm, Intel Corporation |
| R3-224572 | interFrequencyConfig-NoGap signaling from gNB-CU to gNB-DU | Ericsson, Qualcomm, Intel Corporation |
| R3-224574 | How to achieve NSAG configuration at NG-RAN | Ericsson |
| R3-224583 | Correction to NTN-IoT | Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R3-224590 | Correction to R17 QoE | Huawei, China Telecom, China Unicom, Ericsson |
| R3-224603 | Correction of UE Paging Capability | Huawei, Deutsche Telekom, Ericsson, CATT |
| R3-224615 | Discussion on gap type transfer over F1 | ZTE, China Unicom, Lenovo |
| R3-224616 | Discussion on measurement gap enhancements | ZTE, China Unicom, Lenovo |
| R3-224617 | Correction on measurement gap configuration over F1 in Rel-15 | ZTE, China Unicom, Lenovo |
| R3-224618 | Correction on measurement gap configuration over F1 in Rel-16 | ZTE, China Unicom, Lenovo |
| R3-224619 | Correction on measurement gap configuration over F1 in Rel-17 | ZTE, China Unicom, Lenovo |
| R3-224634 | Exchange Served GUAMI List over XnAP | CATT |
| R3-224717 | Discussion on remaining issues for SL relay | ZTE, ChinaTelecom |
| R3-224718 | Corrections on NR SL Relay for TS 38.470 | ZTE, ChinaTelecom, CMCC |
| R3-224719 | Corrections on NR SL Relay for TS 38.401 | ZTE, ChinaTelecom, CMCC |
| R3-224720 | Corrections on NR SL Relay for TS 38.473 | ZTE, ChinaTelecom |
| R3-224725 | Supporting network slice AS group | Huawei, CMCC, ZTE |
| R3-224726 | Supporting network slice AS group | Huawei, CMCC, ZTE |
| R3-224727 | Correction of on-demand SI for connected UE | Huawei, Orange, Deutsche Telekom, BT, Qualcomm |
| R3-224728 | Correction of on-demand SI for connected UE | Huawei, Orange, Deutsche Telekom, BT, Qualcomm |
| R3-224729 | Correction on interFrequencyConfig-NoGap | Huawei, BT, Orange, Deutsche Telekom, ZTE, Samsung |
| R3-224730 | Correction on interFrequencyConfig-NoGap | Huawei, BT, Orange, Deutsche Telekom, ZTE, Samsung, , Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Inc. |
| R3-224734 | Correction on RedCap paging capability to TS38.473 | ZTE, Ericsson, Qualcomm |
| R3-224736 | Left issues about SL relay in Rel-17 | CATT, Samsung,CMCC |
| R3-224737 | Correction to 38.473 for SL relay (R17) | CATT, Samsung,CMCC |
| R3-224738 | Correction to 38.401 for SL relay (R17) | CATT, Samsung |
| R3-224762 | Misalignment with RAN2 in Redcap broadcast information | Xiaomi, Ericsson, CMCC |
| R3-224763 | Correction on RedCap Broadcast Information for TS38.423 | Xiaomi, Ericsson, CMCC |
| R3-224764 | Correction on RedCap Broadcast Information for TS38.473 | Xiaomi, Ericsson, CMCC |
| R3-224778 | Completion of Direct Early Data Forwarding support from source SN during Inter-SN CPC when multiple candidate target SNs are involved | Intel Corporation |
| R3-224779 | Stage-2 Completion of Direct Early Data Forwarding support from source SN during Inter-SN CPC when multiple candidate target SNs are involved | Intel Corporation |
| R3-224780 | X2AP Completion of Direct Early Data Forwarding support from source SN during SN-initiated Inter-SN CPC when multiple candidate target SNs are involved | Intel Corporation |
| R3-224781 | XnAP Completion of Direct Early Data Forwarding support from source SN during SN-initiated Inter-SN CPC when multiple candidate target SNs are involved | Intel Corporation |
| R3-224796 | Discussion on Supporting for target NSSAI during handover | CATT |
| R3-224797 | CR to 38.423 for Target NSSAI during handover | CATT |
| R3-224802 | Transferring CG-SDT configuration and SRS positioning Inactive configuration from DU to CU (option 1) | Ericsson, Xiaomi, Google |
| R3-224803 | Transferring CG-SDT configuration and SRS positioning Inactive configuration from DU to CU (option 2) | Ericsson, Xiaomi, Google |
| R3-224815 | Correction on PO determination for UE in inactive state | Google Inc. |
| R3-224829 | Correction on Rel-17 SDT | Samsung, Nokia, Nokia Shanghai Bell, ZTE, Huawei, China Telecom |
| R3-224843 | Correction of F1-U Delay Measurement for QoS Monitoring | Samsung, Intel Corporation, Verizon Wireless, Huawei, CMCC, KDDI |
| R3-224856 | Correction on QoS Flow Mapping Indication | Samsung, ZTE, China Unicom |
| R3-224857 | Correction on QoS Flow Mapping Indication | Samsung, ZTE, China Unicom |
| R3-224858 | Correction on QoS Flow Mapping Indication | Samsung, ZTE, China Unicom |
| R3-224867 | Discussion on F1-U Delay Measurement for QoS Monitoring | Samsung, Verizon Wireless, Intel Corporation, Huawei, CMCC, KDDI |
| R3-224868 | Correction of F1-U Delay Measurement for QoS Monitoring | Samsung, Intel Corporation, Verizon Wireless, Huawei, CMCC, KDDI |
| R3-224872 | Correction of timing advance report for NR UL E-CID positioning | Huawei, CMCC, China Unicom |
| R3-224873 | Introduction of uplink GapFR2 | Huawei, Orange, Deutsche Telekom |
| R3-224884 | Correction on Location reporting control (NGAP) | ZTE, Huawei, CATT, Samsung |
| R3-224885 | Correction on QoS Flow Mapping Indication | ZTE, Samsung, China Unicom |
| R3-224918 | 38.300 CR Correction on slice group configuration | CMCC,Huawei,ZTE |
| R3-224948 | Introduction of two PHR mode | Huawei |
| R3-224949 | Correction of SIB18 and SIB19 signalling | Huawei, China Telecom, Nokia, Nokia Shanghai Bell |
| R3-224952 | Pending action to RAN3 on the RRC container name | Ericsson, Xiaomi, Google. |
| R3-224958 | Discussion on CHO with SCG configuration | Samsung |
| R3-224965 | Correction to non UE associated signalling | Ericsson |
| R3-224966 | Correction to non UE associated signalling | Ericsson |
| R3-224967 | Correction to non UE associated signalling | Ericsson |
| R3-224968 | Correction to non UE associated signalling | Ericsson |
| R3-224969 | Correction to non UE associated signalling | Ericsson |
| R3-224970 | Correction to non UE associated signalling | Ericsson |
| R3-224997 | CB: # 10_CPAC - Summary of email discussion | Intel - moderator |
| R3-224998 | CB: # 11_R17SDT - Summary of email discussion | Samsung - moderator |
| R3-224999 | CB: # 12_CAG - Summary of email discussion | Huawei - moderator |
| R3-225000 | CB: # 13_PDCPCount_Reset - Summary of email discussion | NEC - moderator |
| R3-225001 | CB: # 14_SliceGroup - Summary of email discussion | CMCC - moderator |
| R3-225002 | CB: # 15_GapRelated - Summary of email discussion | ZTE - moderator |
| R3-225003 | CB: # 16_R17SLRelay - Summary of email discussion | ZTE - moderator |
| R3-225004 | CB: # 17_R17Redcap - Summary of email discussion | Xiaomi - moderator |
| R3-225034 | Stage 2 Clarification on SDT to TS 38.401 | ZTE, China Telecom, CATT, Nokia, Nokia Shanghai Bell, Samsung |
| R3-225035 | interFrequencyConfig-NoGap signaling from gNB-CU to gNB-DU | Ericsson, Qualcomm, Intel Corporation, Apple |
| R3-225036 | interFrequencyConfig-NoGap signaling from gNB-CU to gNB-DU | Ericsson, Qualcomm, Intel Corporation, Apple |
| R3-225039 | Corrections and way forward to Inter Frequency Measurements without Gaps | Ericsson, Qualcomm, Intel Corporation, Apple |
| R3-225045 | Correction on gNB-DU ID | Huawei, Deutsche Telekom, China Unicom |
| R3-225046 | Coordination of CHO and intra-SN CPC | Huawei, Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-225053 | CB: # 51_F1TNLAddress - Summary of email discussion | Nokia - moderator |
| R3-225054 | CB: # 52_XnDataForwarding - Summary of email discussion | Nokia - moderator |
| R3-225055 | Correction on Missing Criticality Diagnostics over E1AP | Huawei, BT, Deutsche Telekom, Orange |
| R3-225056 | Correction to R17 QoE | Huawei, China Telecom, China Unicom, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-225057 | CB: # 53_PagingIssues - Summary of email discussion | Huawei - moderator |
| R3-225059 | R17 CR for TS36.423 on Extending NR Operation to 71GHz | China Telecom, Ericsson |
| R3-225060 | R17 CR for TS38.423 on Extending NR Operation to 71GHz | China Telecom, Ericsson |
| R3-225061 | R17 CR for TS38.473 on Extending NR Operation to 71GHz | China Telecom, Ericsson |
| R3-225063 | CB: # 54_LRC - Summary of email discussion | ZTE - moderator |
| R3-225064 | CB: # 55_SIB1819 - Summary of email discussion | Huawei - moderator |
| R3-225065 | Correction on QoS Flow Mapping Indication | ZTE, Samsung, China Unicom |
| R3-225066 | Correction on QoS Flow Mapping Indication | Samsung, ZTE, China Unicom |
| R3-225067 | Correction on QoS Flow Mapping Indication | Samsung, ZTE, China Unicom |
| R3-225068 | Update for Rel-17 NGAP IEs not applicable to non-3GPP access | Nokia, Nokia Shanghai Bell, Huawei, BT, Ericsson |
| R3-225069 | Correction on gNB-DU ID | Huawei, Deutsche Telekom, China Unicom |
| R3-225070 | Addition of a CHO-related notes to a chapter on HO with DC [CHOwithDCkept] | Nokia, Nokia Shanghai Bell |
| R3-225071 | CB: # 56_DAPSoverF1 - Summary of email discussion | ZTE - moderator |
| R3-225072 | Correction of PRACH optimization | NEC |
| R3-225073 | R17 CR for TS36.423 on Extending NR Operation to 71GHz | China Telecom, Ericsson, Huawei |
| R3-225074 | R17 CR for TS38.423 on Extending NR Operation to 71GHz | China Telecom, Ericsson, Huawei |
| R3-225075 | R17 CR for TS38.473 on Extending NR Operation to 71GHz | China Telecom, Ericsson, Huawei |
| R3-225092 | CAG Access Control without mobility restriction | Nokia, Nokia Shanghai Bell, Huawei, Deutsche Telekom, Orange, Ericsson |
| R3-225093 | CAG Access Control without mobility restricition | Nokia, Nokia Shanghai Bell, Deutsche Telekom, Orange, Ericsson |
| R3-225095 | Correction of Xn data forwarding | Nokia, Nokia Shanghai Bell, Orange, Deutsche Telekom, China Telecom, CATT, Huawei |
| R3-225096 | Correction of Xn data forwarding | Nokia, Nokia Shanghai Bell, Orange, Deutsche Telekom, China Telecom, CATT, Huawei |
| R3-225097 | CAG access control without mobility restrictions | Huawei, Nokia, Nokia Shanghai Bell, Orange, Deutsche Telekom, Ericsson |
| R3-225098 | CAG access control without mobility restrictions | Huawei, Nokia, Nokia Shanghai Bell, Orange, Deutsche Telekom, Ericsson |
| R3-225099 | CAG access control without mobility restrictions | Huawei, Nokia, Nokia Shanghai Bell, Orange, Deutsche Telekom, Ericsson |
| R3-225100 | CAG access control without mobility restrictions | Huawei, Nokia, Nokia Shanghai Bell, Orange, Deutsche Telekom, Ericsson |
| R3-225101 | Clarification on F1 Paging function | Ericsson, Huawei, ZTE, Qualcomm Inc., Nokia, Nokia Shanghai Bell, CATT |
| R3-225102 | Correction of UE Paging Capability | Huawei, Deutsche Telekom, Ericsson, CATT, Nokia, Nokia Shanghai Bell, Google, ZTE |
| R3-225103 | Stage 2 Clarification on SDT to TS 38.401 | ZTE, China Telecom, CATT, Nokia, Nokia Shanghai Bell, Samsung |
| R3-225104 | Clarification to CG based SDT | Google Inc., Huawei |
| R3-225105 | Correction on Rel-17 SDT | Samsung, Nokia, Nokia Shanghai Bell, ZTE, Huawei, China Telecom |
| R3-225107 | Introduction of uplink GapFR2 | Huawei, Orange, Deutsche Telekom, Nokia, Nokia Shanghai Bell |
| R3-225111 | 38.300 CR Correction on slice group configuration | CMCC, Huawei, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R3-225112 | Supporting network slice AS group | Huawei, CMCC, ZTE, Nokia, Nokia Shanghai Bell, Samsung, CATT |
| R3-225114 | Correction to SDT for supporting delta signaling | Google Inc., Huawei, Intel Corporation, Nokia, Nokia Shanghai Bell, Lenovo, China Telecom |
| R3-225115 | Transferring CG-SDT configuration and SRS positioning Inactive configuration from DU to CU (option 1) | Ericsson, Xiaomi, Google, Intel Corporation, China Telecom |
| R3-225117 | Completion of DAPS in case of split gNB deployment to 38.473 | ZTE |
| R3-225118 | Completion of DAPS in case of split gNB deployment to 38.473 | ZTE |
| R3-225134 | Correction on Location reporting control (NGAP) | ZTE, Huawei, CATT, Samsung |
| R3-225135 | Correction on RedCap paging capability to TS38.473 | ZTE, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, Xiaomi |
| R3-225149 | Handling of PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE, Huawei, CATT |
| R3-225150 | Handling of PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE, Huawei, CATT |
| R3-225161 | Correction to 38.401 for SL relay (R17) | CATT, Samsung, ZTE, Nokia, Nokia Shanghai Bell, China Telecom |
| R3-225162 | SL relay corrections | Huawei, Nokia, Nokia Shanghai Bell, China Unicom, CATT, ZTE, ChinaTelecom |
| R3-225181 | Corrections on NR SL Relay for TS 38.470 | ZTE, ChinaTelecom, CMCC, CATT |
| R3-225183 | Correction on measurement gap configuration over F1 in Rel-16 | ZTE, China Unicom, Lenovo |
| R3-225184 | Correction on measurement gap configuration over F1 in Rel-17 | ZTE, China Unicom, Lenovo |
| R3-225185 | Correction to R17 QoE | Huawei, Nokia, Nokia Shanghai Bell, ZTE |
| R3-225192 | Correction of Slice Group Configuration | ZTE, Huawei, CMCC, Samsung, Nokia, Nokia Shanghai Bell, CATT, NEC, LG Electronics |
| R3-225193 | LS on DAPS HO powercordination | ZTE |
| R3-225197 | Interaction between CPC Cancel and SN Release | Ericsson, Lenovo, ZTE, Google, Intel Corporation |
| R3-225202 | Correction of Slice Group Configuration | ZTE, Huawei, CMCC, Samsung, Nokia, Nokia Shanghai Bell, CATT, NEC, LG Electronics |
| R3-225207 | Clarification on direct data forwarding for MN initiated CPC to TS37340 | ZTE, Lenovo, CATT, Huawei, Intel Corporation |
| R3-225220 | Correction of Slice Group Configuration | ZTE, Huawei, CMCC, Samsung, Nokia, Nokia Shanghai Bell, CATT, NEC, LG Electronics |
| R3-225221 | 38.300 CR Correction on slice group configuration | CMCC, Huawei, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Samsung, CATT |
| R3-225225 | Correction of Slice Group Configuration | ZTE, Huawei, CMCC, Samsung, Nokia, Nokia Shanghai Bell, CATT, NEC, LG Electronics |
| R3-225232 | CB: # 17_R17Redcap - Summary of email discussion | Xiaomi - moderator |
| R3-225236 | PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE, Ericsson |
| R3-225237 | PDCP COUNT reset in CU-UP for inter-gNB-DU Handover | NEC, ZTE, Ericsson |
| R3-225242 | (Draft) LS on identifying SSB type for Redcap UE | NEC |
| R3-225269 | Correction on interFrequencyConfig-NoGap | Huawei, BT, Orange, Deutsche Telekom, ZTE, Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Inc. |
| R3-225270 | Correction on interFrequencyConfig-NoGap | Huawei, BT, Orange, Deutsche Telekom, ZTE, Samsung, Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm Inc. |
| R3-225271 | Correction on RedCap paging capability to TS38.473 | ZTE, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, Xiaomi |
| R3-225272 | R17 CR for TS38.473 on Extending NR Operation to 71GHz | China Telecom, Ericsson, Huawei |
| R3-225276 | Correction on RedCap paging capability to TS38.473 | ZTE, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, Xiaomi |
| R3-225277 | Coordination of CHO and intra-SN SCG reconfiguration | ZTE, Nokia, Nokia Shanghai Bell, Huawei, Ericsson, Intel Corporation, CATT |
| R3-225278 | Coordination of CHO and intra-SN SCG reconfiguration | Nokia, Nokia Shanghai Bell, ZTE, Huawei, Ericsson, Intel Corporation, CATT |
| R3-225279 | Coordination of CHO and intra-SN SCG reconfiguration | Huawei, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Intel Corporation, CATT |
| 10.1 | General | |
| R3-224899 | Work Plan for Enhancement of Data Collection for SON_MDT in NR standalone and MR-DC WI | CMCC |
| 10.2 | Support of SON/MDT Enhancements | |
| R3-224390 | Enhanced MRO KPI analysis for NR-U | Nokia, Nokia Shanghai Bell |
| R3-224391 | LS on MRO for NR-U | Nokia, Nokia Shanghai Bell |
| R3-224396 | Discussion on inter-RAT Successful Handover Report | China Telecommunication |
| R3-224397 | Discussion on Successful PScell change report | China Telecommunication |
| R3-224410 | SON enhancements for CPC | Lenovo |
| R3-224411 | SON enhancements for successful PSCell change report | Lenovo |
| R3-224412 | Successful Handover Report for inter-RAT HO | Lenovo |
| R3-224413 | MRO for fast MCG link recovery | Lenovo |
| R3-224414 | MRO for handover failure or SCG failure in NR-U | Lenovo |
| R3-224461 | Discussion related to RACH Report retrieval methods | Nokia, Nokia Shanghai Bell |
| R3-224463 | Initial discussion on performing MDT in NPN networks | Nokia, Nokia Shanghai Bell |
| R3-224508 | NR-U enhancements for UL MLB and MRO | Ericsson |
| R3-224547 | MR-DC CPAC and Fast MCG recovery | Huawei |
| R3-224548 | Successful PScell change report and Successful Handover Report | Huawei |
| R3-224604 | MRO enhancements for CPAC and fast MCG recovery | Qualcomm Incorporated |
| R3-224605 | Successful PSCell change and successful handover scenarios | Qualcomm Incorporated |
| R3-224606 | SON MDT for Non-Public networks | Qualcomm Incorporated |
| R3-224607 | SON enhancements for NR-U and RACH optimization enhancements | Qualcomm Incorporated |
| R3-224620 | Initial consideration on NR-U optimization in Rel-18 | ZTE |
| R3-224697 | Support of MDT in NPN and the continuation of NR-U SON | Huawei |
| R3-224698 | Further enhancement for RACH optimisation | Huawei |
| R3-224743 | Discussion on SON enhancements for MR-DC CPAC | CATT |
| R3-224744 | Discussion on SON Enhancements for Successful PScell change report, SHR, NPN and NR-U | CATT |
| R3-224745 | Discussion on SON enhancements for RACH report and fast MCG recovery | CATT |
| R3-224746 | LS on SON enhancement for RA report and fast MCG recovery | CATT |
| R3-224821 | SON enhancements for CPAC | Samsung |
| R3-224823 | SON enhancement for MCG failure recovery | Samsung |
| R3-224824 | SON enhancement for Successful Handover Report | Samsung |
| R3-224847 | Discussion on SON for NR-U | Samsung |
| R3-224848 | Discussion on SON for RACH | Samsung |
| R3-224900 | SONMDT enhancement for fast MCG recovery | CMCC |
| R3-224901 | SONMDT enhancement for RACH report | CMCC |
| R3-224903 | SONMDT enhancement for MR-DC CPAC | CMCC |
| R3-224922 | Initial consideration on SON related features | ZTE |
| R3-224923 | Initial consideration on RACH enhancement | ZTE |
| R3-224924 | Initial consideration on MDT support in NPN | ZTE |
| R3-224928 | SON enhancements for Non-public networks | Ericsson |
| R3-224929 | SON enhancements for RACH Optimization | Ericsson |
| R3-224931 | SON enhancements for Mobility Robustness | Ericsson |
| R3-225006 | CB: # SONMDT1_SONMDT - Summary of email discussion | Nokia - moderator |
| R3-225007 | CB: # SONMDT2_NRU - Summary of email discussion | Ericsson - moderator |
| R3-225113 | LS on NR-U support for MRO | Ericsson |
| R3-225120 | CB: # SONMDT1_SONMDT - Summary of email discussion | Nokia - moderator |
| R3-225121 | CB: # SONMDT2_NRU - Summary of email discussion | Ericsson - moderator |
| R3-225122 | LS on NR-U support for MRO | Ericsson |
| R3-225196 | LS on the scope for the support of SON/MDT enhancements | Nokia |
| R3-225238 | LS on the scope for the support of SON/MDT enhancements | Nokia |
| R3-225240 | CB: # SONMDT2_NRU - Summary of email discussion | Ericsson - moderator |
| R3-225241 | LS on NR-U support for MRO | Ericsson |
| 10.3 | Support of Data Collection for MRO | |
| R3-224415 | (TP for SON BLCR for 38.300) MRO for inter-system handover for voice fallback | Lenovo |
| R3-224549 | MRO for MR-DC SCG failure scenario | Huawei |
| R3-224550 | MRO enhancement for inter-system handover voice fallback | Huawei |
| R3-224608 | MRO enhancements for inter-system handover voice fall back and MR-DC SCG failures | Qualcomm Incorporated |
| R3-224621 | Support of Data Collection for MRO | ZTE |
| R3-224747 | Discussion on MRO for MR-DC SCG failure scenario | CATT |
| R3-224748 | Discussion on MRO enhancement for inter-system handover voice fallback | CATT |
| R3-224822 | Discussion on MR-DC SCG failure and MR-DC CPAC | Samsung |
| R3-224902 | MRO for inter-system voice fallback | CMCC |
| R3-225008 | CB: # SONMDT3_MRO - Summary of email discussion | Lenovo - moderator |
| 10.4 | Others | |
| R3-224462 | RAN3 aspects of signalling based logged MDT override protection in Rel-18 | Nokia, Nokia Shanghai Bell |
| R3-224609 | Signaling based logged MDT override protection | Qualcomm Incorporated |
| R3-224925 | Other features releated to SON_MDT | ZTE |
| R3-225009 | SONMDT4_Others - Summary of email discussion | Qualcomm - moderator |
| 11.1 | General | |
| R3-224842 | Workplan for Rel-18 NR QoE Enhancement | China Unicom |
| 11.2 | Support for New Service Type and RRC_INACTIVE/RRC_IDLE states | |
| R3-224360 | QMC Support for New Services and High-Mobility Scenarios | Ericsson |
| R3-224361 | QoE and RVQoE Measurement Support for MBS | Ericsson |
| R3-224416 | Discussion on the objectives of QoE enhancements | Lenovo |
| R3-224417 | QoE measurement configuration and collection in RRC_INACTIVE and RRC_IDLE | Lenovo |
| R3-224418 | (TP to 38.423 & 38.420) Support of QoE measurement in RRC_INACTIVE | Lenovo |
| R3-224457 | On support of QMC for MBS and other service types surviving idle mode | Nokia, Nokia Shanghai Bell |
| R3-224459 | Initial observations on QMC support for Augmented Reality | Nokia, Nokia Shanghai Bell |
| R3-224610 | QoE for new service types and high mobility scenarios | Qualcomm Incorporated |
| R3-224611 | QoE in RRC_IDLE and RRC_INACTIVE for MBS broadcast service | Qualcomm Incorporated |
| R3-224758 | Discussion on QMC in RRC_INACTIVE RRC_IDLE states | Xiaomi |
| R3-224788 | Discussion on NR QoE for new service type | CATT |
| R3-224789 | Discussion on NR QoE in RRC_INACTIVE/ RRC_IDLE states | CATT |
| R3-224840 | NR QoE Discussion on support for new service type and RRC inactive-idle state | Samsung |
| R3-224864 | Discussion on QoE measurement in RRC_INACTIVE and RRC_IDLE states | China Unicom |
| R3-224875 | Discussion on INACTIVE/IDLE QoE | ZTE Corporation |
| R3-224876 | Discussion on new service types and high mobility scenario | ZTE Corporation |
| R3-224886 | General considerations on R18 QoE enhancements | Huawei |
| R3-224887 | [Draft] LS to SA4 on R18 enhancement of NR QoE management and optimizations for diverse services | Huawei |
| R3-224888 | Initial discussions on the support of QoE measurement in RRC_INACTIVE and RRC_IDLE states for MBS service | Huawei |
| R3-225010 | CB: # QoE1_Inactive_Idle - Summary of email discussion | ZTE - moderator |
| R3-225077 | CB: # QoE1_Inactive_Idle - Summary of email discussion | ZTE - moderator |
| R3-225088 | LS on new service types for NR QoE | ZTE |
| R3-225233 | CB: # QoE1_Inactive_Idle - Summary of email discussion | ZTE - moderator |
| R3-225255 | LS on new service types for NR QoE | ZTE |
| 11.3 | Support QoE for NR-DC | |
| R3-224362 | The Support for QoE and RVQoE Measurement and Reporting in NR-DC Scenarios | Ericsson |
| R3-224419 | QoE measurement in NR-DC | Lenovo |
| R3-224420 | (TP to TS 38.420) Support of QoE measurement in NR-DC | Lenovo |
| R3-224458 | On support for QMC in NR-DC | Nokia, Nokia Shanghai Bell |
| R3-224612 | Support for QoE in NR-DC | Qualcomm Incorporated |
| R3-224759 | Discussion on QoE in NR-DC | Xiaomi |
| R3-224790 | Discussion on Support for legacy QoE in NR-DC | CATT |
| R3-224791 | Discussion on Support for RAN visible QoE in NR-DC | CATT |
| R3-224841 | NR QoE Discussion on support for NR-DC | Samsung |
| R3-224865 | Discussion on QoE measurement in NR-DC | China Unicom |
| R3-224889 | Discussions on the support for QoE in NR-DC | Huawei |
| R3-224936 | Discussion on the configuration and reporting of QoE and RVQoE in NR-DC | ZTE |
| R3-224937 | Discussion on MDT alignment and continuity in NR-DC | ZTE |
| R3-225011 | CB: # QoE2_NRDC - Summary of email discussion | China Unicom - moderator |
| R3-225078 | CB: # QoE2_NRDC - Summary of email discussion | China Unicom - moderator |
| R3-225199 | Draft LS on Support for Reporting of RAN Visible QoE Measurements | China Unicom |
| R3-225234 | LS to RAN2 on RAN3 agreement of QoE reporting in NR-DC | China Unicom |
| R3-225235 | CB: # QoE2_NRDC - Summary of email discussion | China Unicom - moderator |
| R3-225256 | LS to RAN2 on RAN3 agreement of QoE reporting in NR-DC | China Unicom |
| 11.4 | Left-over from R17 | |
| R3-224227 | Consideration on Slice Grouping and Slice | PML |
| R3-224228 | Enable QoE reporting of Network Slice Groups and Slice(F1AP) | PML |
| R3-224229 | Enable QoE reporting of Network Slice Groups and Slice(XnAP) | PML |
| R3-224363 | The Enhancements of RAN Visible QoE Measurements and Reporting | Ericsson |
| R3-224364 | The Enhancements of QMC Rel-17 Features | Ericsson |
| R3-224460 | QMC enhancements for RAN overload | Nokia, Nokia Shanghai Bell |
| R3-224589 | Discussion on the support of R17 left-over features | Huawei |
| R3-224613 | Enhancements to RAN visible QoE | Qualcomm Incorporated |
| R3-224760 | Discussion on RVQoE value | Xiaomi |
| R3-224761 | Discussion on event-triggered RVQoE | Xiaomi |
| R3-224792 | Discussion on Left-over issues | CATT |
| R3-224839 | NR QoE Discussion on left over from R17 | Samsung |
| R3-224866 | Further discussion on R17 leftover issues | China Unicom |
| R3-224869 | Draft LS for R17 leftover issues | China Unicom |
| R3-224938 | Discussion on R17 QoE left-over issues | ZTE |
| R3-225012 | CB: # QoE3_Others - Summary of email discussion | Huawei - moderator |
| R3-225079 | CB: # QoE3_Others - Summary of email discussion | Huawei - moderator |
| R3-225182 | Draft LS to SA4 on R18 enhancement of NR QoE | Huawei |
| R3-225226 | CB: # QoE3_Others - Summary of email discussion | Huawei - moderator |
| R3-225227 | LS to SA4 on Rel-18 enhancement of NR QoE | Huawei |
| 12.1 | General | |
| R3-224910 | Work plan for AI for RAN | CMCC, Ericsson |
| 12.2 | Data Collection Enhancements and Signaling Support | |
| R3-224226 | Consideration on use case of mobility optimization | PML |
| R3-224298 | discussion paper | NEC |
| 12.2.1 | Stage2 Related | |
| R3-224307 | AI/ML information exchange for NG based handover | Qualcomm India Pvt Ltd |
| R3-224308 | UE impacts in NG-RAN AI/ML | Qualcomm India Pvt Ltd |
| R3-224421 | (TP for TS38.300 TS38.401) Discussion on general framework | Lenovo |
| R3-224427 | Discussion on AI for NR DC scenario | Lenovo |
| R3-224492 | User consent for AI/ML processes | Ericsson |
| R3-224493 | MDT enhancements to support AI/ML based processes | Ericsson |
| R3-224494 | Guidelines and way forward on AI/ML normative work | Ericsson |
| R3-224563 | Feedback Collection after an AI/ML Action | Nokia, Nokia Shanghai Bell |
| R3-224564 | Predictions Exchange between NG-RAN Nodes | Nokia, Nokia Shanghai Bell |
| R3-224565 | Revisiting User Consent for the Purpose of Data Collection for AI/ML | Nokia, Nokia Shanghai Bell |
| R3-224566 | Discussion on AI/ML Model Output Validity Time | Nokia, Nokia Shanghai Bell |
| R3-224659 | Discussion on Stage-2 descriptions of AI/ML | CATT |
| R3-224660 | TP on TS 38.300 for AI/ML | CATT |
| R3-224661 | TP on TS 38.401 for AI/ML | CATT |
| R3-224771 | Discussion on Common Aspects in Stage 2 of AI/ML based Use Cases | Intel Corporation |
| R3-224772 | Discussion on Stage 2 of AI/ML based network energy saving and mobility optimization | Intel Corporation |
| R3-224773 | (TP for NR_AIML_NGRAN BL CR for TS 38.300) | Intel Corporation |
| R3-224849 | Discussion on AI for NG-RAN Stage 2 | Samsung |
| R3-224879 | Discussion on AI-RAN Function Feature | ZTE |
| R3-224880 | CR to TS38.300 for addition of AI/ML RAN feature | ZTE |
| R3-224890 | General considerations on support RAN AI&ML in R18 | Huawei |
| R3-224891 | Introduction of RAN AI/ML | Huawei |
| R3-224907 | Considerations on Rel-18 AI ML for NG-RAN | CMCC |
| R3-224908 | Open issues for AI ML for NG-RAN | CMCC |
| R3-224911 | Draft CR to 38.300 on AI ML for NG-RAN | CMCC |
| R3-224912 | Draft CR to 38.401 on AI ML for NG-RAN | CMCC |
| R3-225013 | CB: # AIRAN1_General_Stage2 - Summary of email discussion | CMCC - moderator |
| R3-225058 | Draft CR to 38.401 on AI ML for NG-RAN | CMCC |
| R3-225110 | Draft CR to 38.300 on AI/ML for NG-RAN | CMCC, ZTE |
| R3-225189 | Draft CR to 38.300 on AI/ML for NG-RAN | CMCC, ZTE, Ericsson |
| R3-225211 | Draft CR to 38.300 on AI/ML for NG-RAN | CMCC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, Samsung, Lenovo, Intel Corporation |
| 12.2.2 | Stage3 Related | |
| R3-224231 | AI/ML parameter Open Issue List Discussion | InterDigital |
| R3-224232 | Validity Time Discussion | InterDigital |
| R3-224254 | AI/ML Radio Measurement Discussion | InterDigital |
| R3-224255 | AI/ML UE location Discussion | InterDigital |
| R3-224256 | Discussion on Mobility Optimization Model Outputs | InterDigital |
| R3-224257 | Discussion on Load Balancing Model Outputs | InterDigital Finland Oy |
| R3-224258 | QoS Feedback | InterDigital |
| R3-224306 | XN enhancements for NG-RAN AI/ML | Qualcomm India Pvt Ltd |
| R3-224359 | Discussion on data collection enhancements and signaling support | NTT DOCOMO, INC. |
| R3-224422 | Discussion on resource status prediction | Lenovo |
| R3-224423 | Discussion on UE traffic prediction | Lenovo |
| R3-224424 | Discussion on AI assisted network energy saving | Lenovo |
| R3-224425 | Discussion on prediction and feedback transfer in mobility scenario | Lenovo |
| R3-224426 | (TP for TS37.483 TS37.480) Support UE traffic prediction over E1 interface | Lenovo |
| R3-224488 | AI/ML Network Energy Saving | Ericsson |
| R3-224489 | AI/ML Load Balancing | Ericsson |
| R3-224490 | AI/ML Mobility Optimization | Ericsson |
| R3-224491 | BL CR to TS 38.423: Support for AI/ML in NG-RAN | Ericsson |
| R3-224560 | AI/ML Network Energy Saving | Nokia, Nokia Shanghai Bell |
| R3-224561 | AI/ML Load Balancing | Nokia, Nokia Shanghai Bell |
| R3-224562 | AI/ML Mobility Optimization | Nokia, Nokia Shanghai Bell |
| R3-224655 | Discussion on AI/ML deployment and Stage-3 impacts | CATT |
| R3-224656 | TP on TS 37.483 for AI/ML | CATT |
| R3-224657 | TP on TS 38.423 for AI/ML | CATT |
| R3-224658 | TP on TS 38.473 for AI/ML | CATT |
| R3-224675 | Discussion on remaining issues of Mobility Optimization | VIVO TECH GmbH |
| R3-224716 | Discussion on stage 3 related impacts of mobility optimization | LG Electronics |
| R3-224770 | Discussion on Data Collection and Signaling Support of AI/ML for NG-RAN | Intel Corporation |
| R3-224774 | Discussion on Common Aspects in Stage 3 of AI/ML based Use cases | Intel Corporation |
| R3-224775 | Discussion on Stage 3 of AI/ML based network energy saving and mobility optimization | Intel Corporation |
| R3-224776 | (TP for NR_AIML_NGRAN BL CR for TS 38.423) | Intel Corporation |
| R3-224850 | Discussion on AI/ML based Network Energy Saving (Stage 3) | Samsung |
| R3-224851 | Discussion on AI/ML based Load Balancing (Stage 3) | Samsung |
| R3-224852 | Discussion on AI/ML based Mobility Optimization (Stage 3) | Samsung |
| R3-224853 | Correction of AI/ML for NG-RAN | Samsung |
| R3-224854 | Correction of AI/ML for NG-RAN | Samsung |
| R3-224855 | Correction of AI/ML for NG-RAN | Samsung |
| R3-224874 | Discussion of potential impacts on signalling procedures | China Unicom |
| R3-224881 | Discussion on AI/ML energy saving strategy | China Unicom |
| R3-224882 | Discussion on AI/ML resource status | China Unicom |
| R3-224892 | Introduction of RAN AI/ML | Huawei |
| R3-224893 | Introduction of RAN AI/ML | Huawei |
| R3-224894 | Discussion on the support of mobility enhancements using AI&ML | Huawei |
| R3-224895 | Discussion on the support of load balancing using AI&ML | Huawei |
| R3-224896 | Discussion on the support of energy saving using AI&ML | Huawei |
| R3-224909 | Stage 3 issues on Rel-18 AI ML for NG-RAN | CMCC |
| R3-224957 | Signalling Procedure to support AI/ML in RAN | China Telecom |
| R3-224960 | Discussion on the standard impacts of AI-RAN | ZTE |
| R3-224961 | Discussion on standards impacts of load prediction across multiple AI/ML based use cases | ZTE |
| R3-224962 | Discussion on standards impacts of trajectory prediction across multiple AI/ML based use cases | ZTE |
| R3-224963 | CR to TS38.423 for the unified AI/ML procedure | ZTE |
| R3-224964 | CR to TS38.423 to enhance the existing procedure for AIML function | ZTE |
| R3-224978 | Data collection via MDT in split architecture | Beijing Xiaomi Mobile Software |
| R3-224983 | discussion on measurements of R18 AI for RAN | CMCC |
| R3-225014 | CB: # AIRAN2_Stage3 - Summary of email discussion | ZTE - moderator |
| R3-225123 | CB: # AIRAN2_Stage3 - Summary of email discussion | ZTE - moderator |
| R3-225243 | CB: # AIRAN2_Stage3 - Summary of email discussion | ZTE - moderator |
| 13.1 | General | |
| R3-224237 | Workplan for Rel-18 mobile IAB | Qualcomm Inc. (Rapporteur) |
| R3-224375 | Discussion on general mobile IAB aspects | Nokia, Nokia Shanghai Bell |
| R3-224428 | Discussion on multi-hop backhauling for mobile IAB | Lenovo |
| R3-224495 | Clarifications of Rel-18 Mobile IAB Work Item Scope | Ericsson |
| R3-224502 | Workplan for Rel-18 mobile IAB | Qualcomm Inc. (Rapporteur) |
| R3-224786 | Discussion on multi-hop scenario for mobile IAB-node | Intel Corporation, Qualcomm, Huawei, Ericsson, Nokia, InterDigital |
| R3-224825 | Discussion on potential complexity of single-hop and multi-hop scenarios | samsung |
| R3-225029 | CB: # IAB1_General - Summary of email discussion | Qualcomm - moderator |
| 13.2 | Support IAB-node mobility | |
| R3-224238 | Topology adaptation for mobile IAB | Qualcomm Inc. |
| R3-224353 | Discussion on the full migration for mobile IAB | Huawei |
| R3-224354 | Discussion on the inter-donor transport for full migration of mobile IAB | Huawei |
| R3-224376 | IAB mobility | Nokia, Nokia Shanghai Bell |
| R3-224377 | Discussion on mobile IAB aspects based on dual-DU | Nokia, Nokia Shanghai Bell |
| R3-224429 | Inter-donor full migration procedure of mobile IAB | Lenovo |
| R3-224496 | The Migration Procedure for Mobile IAB-Nodes | Ericsson |
| R3-224504 | Topology adaptation for mobile IAB | Qualcomm Inc. |
| R3-224704 | Support of intra-m-CU mobility | Fujitsu |
| R3-224705 | Discussion on IAB full migration | Fujitsu |
| R3-224710 | Discussion on inter-donor full migration in mobile IAB scenario | ZTE |
| R3-224711 | Discussion on migration sequence of full migration procedure | ZTE |
| R3-224767 | Discussion on IAB full migration | Xiaomi |
| R3-224777 | Discussion on Full Migration of mobile IAB-node | Intel Corporation |
| R3-224826 | Discussion on full migration procedure | samsung |
| R3-225030 | CB: # IAB2_Mobility - Summary of email discussion | Ericsson - moderator |
| 13.3 | Mobility Enhancements | |
| R3-224233 | Handling legacy UE in UAM using Mobile-IAB | KT Corp., LG Uplus, SK Telecom, ETRI |
| R3-224239 | Enhancements for mobility of IAB-node and its served UEs | Qualcomm Inc. |
| R3-224355 | Discussion on group mobility for mobile IAB and Ues | Huawei |
| R3-224356 | Discussion on RACH optimization for connected UE of mobile IAB | Huawei |
| R3-224378 | Discussion on mobility enhancements | Nokia, Nokia Shanghai Bell |
| R3-224430 | Mobility enhancements for mobile IAB-node and its served UE | Lenovo |
| R3-224431 | (TP to TS 38.401) Support for group mobility of mobile IAB-node. | Lenovo |
| R3-224497 | Enhancements for IAB-Node Mobility IAB | Ericsson |
| R3-224498 | paper | Ericsson |
| R3-224505 | Enhancements for mobility of IAB-node and its served UEs | Qualcomm Inc. |
| R3-224706 | Update of location information for cells of mobile IAB | Fujitsu |
| R3-224712 | Reduction of UE migration in mobile IAB scenario | ZTE |
| R3-224713 | Discussion on location update of UEs served by mobile IAB | ZTE |
| R3-224768 | Discussion on group mobility | Xiaomi |
| R3-224827 | Discussion on mobility enhancements | samsung |
| R3-225031 | CB: # IAB3_MobEnh - Summary of email discussion | Huawei - moderator |
| R3-225153 | CB: # IAB3_MobEnh - Summary of email discussion | Huawei - moderator |
| 13.4 | Mitigation of interference | |
| R3-224240 | PCI collision avoidance for mobile IAB | Qualcomm Inc. |
| R3-224357 | Discussion on the interference mitigation | Huawei |
| R3-224379 | Interference mitigation for mobile IAB | Nokia, Nokia Shanghai Bell |
| R3-224432 | Interference mitigation of mobile IAB-node mobility | Lenovo |
| R3-224499 | Mitigation of Interference and Reference Signal Collisions for Mobile IAB-Nodes | Ericsson |
| R3-224506 | PCI collision avoidance for mobile IAB | Qualcomm Inc. |
| R3-224707 | Avoidance of resource collisions due to IAB-node mobility | Fujitsu |
| R3-224714 | Discussion on mitigation of interference in mobile IAB scenario | ZTE |
| R3-224769 | Discussion on mitigation of interference | Xiaomi |
| R3-224828 | Discussion on mitigation of interference | samsung |
| R3-225032 | CB: # IAB4_IntMit - Summary of email discussion | ZTE - moderator |
| R3-225154 | CB: # IAB4_IntMit - Summary of email discussion | ZTE - moderator |
| 14.1 | General | |
| R3-224277 | RAN3 Work Plan for Rel-18 Further NR Mobility Enhancements WI | MediaTek Inc., Apple, Huawei |
| 14.2 | Signaling Support for L1/L2 based Inter-Cell Mobility | |
| R3-224278 | Discussion on L1/L2 Mobility Procedures | Nokia, Nokia Shanghai Bell |
| R3-224279 | Discussion on Additional Considerations for L1/L2 Mobility | Nokia, Nokia Shanghai Bell |
| R3-224286 | Discussion of L1/L2 based Inter-Cell Mobility | NTT DOCOMO INC. |
| R3-224296 | Support for L1/L2 based inter-cell mobility | NEC |
| R3-224341 | Discussion on potential impacts on F1 interface for L1/L2 based mobility | vivo |
| R3-224342 | Discussion on collision between L1/L2 based mobility and L3 mobility | vivo |
| R3-224393 | Consideration on support of L1/L2 based Inter-Cell Mobility | China Telecommunication |
| R3-224433 | Discussion on L1/L2 based inter-cell mobility | Lenovo |
| R3-224434 | (TP to TS 38.401) Support of L1/L2 based inter-cell mobility | Lenovo |
| R3-224435 | (TP to TS 38.470) Support of L1/L2 based inter-cell mobility | Lenovo |
| R3-224512 | Signalling Support for L1/L2 based Inter-Cell Mobility | Qualcomm Incorporated |
| R3-224517 | Solutions for L1/L2 based inter-cell mobility | Ericsson |
| R3-224518 | Procedures for configuration of L1/L2 based inter-cell mobility | Ericsson |
| R3-224641 | Initial Considerations on L1/L2 mobility | CATT |
| R3-224642 | Correction to 38.473 for L1/L2-based mobility | CATT |
| R3-224699 | Consideration on intra-DU L1/L2 mobility procedure | Huawei |
| R3-224700 | Consideration on intra-CU inter-DU L1/L2 mobility procedure | Huawei |
| R3-224753 | Discussion of L1/L2 based Inter-Cell Mobility | NTT DOCOMO INC. |
| R3-224756 | Discussion of L1/L2 based Inter-Cell Mobility | NTT DOCOMO INC. |
| R3-224830 | Discussion on L1/L2 based Inter-cell Mobility | Samsung |
| R3-224913 | Initial Considerations on L1/L2 based Inter-Cell Mobility | CMCC |
| R3-224934 | L1/L2 handover procedure | Huawei |
| R3-224954 | CU/DU coordination for L1/L2 based mobility | ZTE |
| R3-224955 | F1AP enhancement for L1/L2 based mobility | ZTE |
| R3-225017 | CB: # MobilityEnh1_L1L2Mo - Summary of email discussion | Huawei - moderator |
| R3-225082 | CB: # MobilityEnh1_L1L2Mo - Summary of email discussion | Huawei - moderator |
| 14.3 | Support CHO in NR-DC | |
| R3-224251 | Continuation of the work on CHO with DC and optimisation of the data forwarding | Nokia, Nokia Shanghai Bell |
| R3-224252 | CHO with multiple candidate SCGs | Nokia, Nokia Shanghai Bell |
| R3-224269 | Discussion on CHO with CPA | ZTE |
| R3-224270 | New procedure for support of CHO with CPA feature to TS37.340 | ZTE |
| R3-224322 | Consideration on CHO related aspects | Huawei |
| R3-224343 | Support of CHO with CPAC | vivo |
| R3-224394 | Consideration on support of CHO including target MCG and SCGs | China Telecommunication |
| R3-224436 | Discussion on CHO in NR-DC | Lenovo |
| R3-224509 | CHO including target MCG and candidate SCGs | Qualcomm Incorporated |
| R3-224519 | Outstanding issues for CHO + MR-DC | Ericsson |
| R3-224520 | Introduction of signaling flows for CHO+MR-DC | Ericsson |
| R3-224793 | Discussion on the scenarios of CHO with multiple candidate SCGs | CATT |
| R3-224794 | Discussion on the procedure of CHO with multiple candidate SCGs | CATT |
| R3-224834 | (TP to TS37.340 on Mobility Enhancements)Considerations on CHO+CPAC procedure | Samsung |
| R3-224835 | (TP to TS38.423 on Mobility Enhancements) Considerations on CHO+CPAC configuration | Samsung |
| R3-225018 | CB: # MobilityEnh2_CHO - Summary of email discussion | Nokia - moderator |
| R3-225083 | CB: # MobilityEnh2_CHO - Summary of email discussion | Nokia - moderator |
| 14.4 | Others | |
| R3-224253 | NR-DC with selective activation of cell groups | Nokia, Nokia Shanghai Bell |
| R3-224271 | Discussion on NR-DC with selective activation of the cell groups | ZTE |
| R3-224287 | Duscussion of selective activation | NTT DOCOMO INC. |
| R3-224297 | NR-DC with selective activation of the cell groups | NEC |
| R3-224323 | Consideration on NR-DC with selective activation of SCG | Huawei |
| R3-224344 | Subsequent CPC/CPA after PSCell Change | vivo |
| R3-224395 | Consideration on support of subsequent CPC/CPA | China Telecommunication |
| R3-224437 | On selective cell group activation | Lenovo |
| R3-224511 | Configuration and activation of multiple cell groups in NR-DC | Qualcomm Incorporated |
| R3-224521 | NR-DC with selective activation | Ericsson |
| R3-224795 | Discussion on NR-DC with selective activation of the cell groups | CATT |
| R3-224836 | Considerations on selective activation of the cell groups | Samsung |
| R3-225019 | CB: # MobilityEnh3_Others - Summary of email discussion | Qualcomm - moderator |
| R3-225085 | CB: # MobilityEnh3_Others - Summary of email discussion | Qualcomm - moderator |
| 15.1 | General | |
| R3-224218 | Reply LS on UE capabilities for MBS | RAN |
| R3-224649 | Rel-18 NR MBS enhancement work plan | CATT |
| R3-225257 | Proposal on Baseline CR assignment for Rel-18 MBS enhancement WID | CATT |
| 15.2 | Support for MBS reception in RAN sharing scenarios | |
| R3-224244 | Support of MBS in RAN sharing scenarios | Qualcomm Incorporated |
| R3-224299 | MBS RAN sharing scenario | NEC |
| R3-224325 | Consideration on MBS reception in RAN sharing scenarios | Huawei, CBN |
| R3-224479 | On NR MBS Rel-18 RAN sharing | Ericsson |
| R3-224650 | Discussion on efficient MBS reception in RAN sharing scenario | CATT |
| R3-224651 | [Draft]LS on the scope of efficient MBS reception in RAN sharing scenario | CATT |
| R3-224862 | Initial discussion on the MBS RAN sharing | Samsung |
| R3-224914 | Discussion on MBS reception in RAN sharing scenarios | CMCC |
| R3-224946 | MBS reception in RAN sharing scenarios | ZTE |
| R3-224947 | draft LS on MBS reception in RAN sharing scenarios | ZTE |
| R3-225015 | CB: # MBS1_NetworkSharing - Summary of email discussion | Samsung - moderator |
| R3-225087 | CB: # MBS1_NetworkSharing - Summary of email discussion | Samsung - moderator |
| R3-225163 | LS on the scope of efficient MBS reception in RAN sharing scenario | CATT |
| R3-225219 | LS on the scope of resource efficient MBS reception in RAN sharing scenario | CATT |
| R3-225229 | LS on the scope of resource efficiency for MBS reception in RAN sharing scenario | CATT |
| 15.3 | Support for RRC_INACTIVE state | |
| R3-224245 | Enhancements to support Multicast reception by UEs in RRC_INACTIVE state | Qualcomm Incorporated |
| R3-224300 | MBS Inactive Reception | NEC |
| R3-224301 | CR for RRC_INACTIVE MBS interested indication in 38.473 | NEC |
| R3-224326 | Multicast reception by UEs in RRC_INACTIVE state | Huawei, CBN |
| R3-224348 | Discussion on Mobility Handling During Multicast Reception in RRC Inactive State | TCL Communication Ltd. |
| R3-224438 | PTM configuration for multicast reception in RRC_INACTIVE | Lenovo |
| R3-224439 | Mobility and state transition for multicast reception in RRC_INACTIVE | Lenovo |
| R3-224529 | Principles for RAN support of Multicast in RRC INACTIVE state | Nokia, Nokia Shanghai Bell |
| R3-224531 | Principles for mobility and state transition for Multicast in RRC INACTIVE state | Nokia, Nokia Shanghai Bell |
| R3-224532 | Dual Delivery Mode Support and Backwards Compatibility issues for multicast in RRC Inactive state | Nokia, Nokia Shanghai Bell |
| R3-224581 | Support of multicast reception in RRC_INACTIVE state - the bigger picture | Ericsson |
| R3-224652 | Initial thought on RAN3 aspects of multicast over RRC INACTIVE | CATT |
| R3-224664 | Comparison of MCCH solution and RRC Dedicated signalling solution | Huawei, CBN |
| R3-224915 | Multicast Reception in RRC_INACTIVE state | CMCC |
| R3-224945 | Multicast reception in RRC_INACTIVE | ZTE |
| R3-225016 | CB: # MBS2_Inactive - Summary of email discussion | CATT - moderator |
| 16.1 | General | |
| R3-224749 | Work plan for NR sidelink relay enhancements | LG Electronics |
| 16.2 | Support Relay and Remote UE Authorization | |
| R3-224370 | Discussion on UE authorization for U2U relay | ZTE |
| R3-224380 | Authorization information for multi-path | Nokia, Nokia Shanghai Bell |
| R3-224551 | SL relay: U2U relay | Huawei |
| R3-224600 | Authorization for multi-path support and U2U relays | Qualcomm Incorporated |
| R3-224750 | Discussion on authorization for UE-to-UE relay operation | LG Electronics |
| R3-224757 | Authorization Enhancement to support Rel.18 Sidelink Relay | Samsung |
| R3-224904 | Consideration on authorization for U2U relay | CMCC |
| R3-225020 | CB: # SLRelay1_Authorization - Summary of email discussion | ZTE - moderator |
| 16.3 | Support Service Continuity Enhancements | |
| R3-224371 | Discussion on Service continuity enhancement for U2N relay | ZTE |
| R3-224381 | Discussion on Support Service Continuity Enhancements | Nokia, Nokia Shanghai Bell |
| R3-224398 | Service continuity for L2 U2N relay | China Telecommunication |
| R3-224522 | Service Continuity Enhancements for Layer-2 UE-to-Network Relays | Ericsson |
| R3-224523 | RAN decision on selection of the target Relay UE | Ericsson |
| R3-224552 | SL relay: Inter-gNB mobility | Huawei |
| R3-224601 | Service continuity enhancements for L2 relays | Qualcomm Incorporated |
| R3-224739 | Support Service Continuity Enhancements for SL relay | CATT |
| R3-224740 | Correction to 38.423 for SL relay (R18) | CATT |
| R3-224751 | Service continuity enhancements for L2 U2N relay | LG Electronics |
| R3-224832 | (TP to TS 38.401) Initial discussion on service continuity enhancement | Samsung |
| R3-224905 | Service continuity for U2N relay | CMCC |
| R3-225021 | CB: # SLRelay2_ServiceContinuity - Summary of email discussion | Ericsson - moderator |
| R3-225084 | CB: # SLRelay2_ServiceContinuity - Summary of email discussion | Ericsson - moderator |
| 16.4 | Multi-path Support | |
| R3-224345 | Authorization and mobility for Multi-path UE aggregation | vivo |
| R3-224372 | Initial considerations on multi-path support | ZTE |
| R3-224382 | Discussion on multi-path support | Nokia, Nokia Shanghai Bell |
| R3-224392 | On multi-path support for sidelink relay | China Telecommunication |
| R3-224524 | Multi-path support with Direct path and Indirect path | Ericsson |
| R3-224553 | SL relay: Multi-path relay and UE aggregation | Huawei |
| R3-224602 | Multi-path support for sidelink relays | Qualcomm Incorporated |
| R3-224741 | Multi-path Support for SL relay | CATT |
| R3-224752 | Multi-path relaying for NR sidelink relay enhancements | LG Electronics |
| R3-224831 | (TP to TS38.401 on SL Relay) Discussion on multipath for sidelink relay | Samsung |
| R3-224906 | Multi-path and UE aggregation | CMCC |
| R3-225022 | CB: # SLRelay3_Others - Summary of email discussion | LG Electronics - moderator |
| R3-225086 | CB: # SLRelay3_Others - Summary of email discussion | LG Electronics - moderator |
| 17.1 | General | |
| R3-224235 | R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 | THALES |
| 17.2 | Support Mobility and Service Continuity Enhancements | |
| R3-224304 | XN Enhancements for NTN Mobility and Feeder Link Switch Over | Qualcomm India Pvt Ltd |
| R3-224305 | NTN Mobility Enhancements for Rel18 | Qualcomm India Pvt Ltd |
| R3-224383 | Discussion on the Mobility and Service Continuity Enhancements in NR NTN | Nokia, Nokia Shanghai Bell |
| R3-224399 | Mobility and service continuity enhancement for NTN | China Telecommunication |
| R3-224440 | Xn interface enhancements in NTN | InterDigital |
| R3-224579 | CHO for NTN | Ericsson, Thales |
| R3-224580 | CHO for NTN – XnAP Impacts | Ericsson, Thales |
| R3-224587 | Enhancement on mobility of NTN | Huawei |
| R3-224588 | Discussion on mobility of NTN | Huawei |
| R3-224622 | Initial consideration on mobility issue for NR NTN | ZTE |
| R3-224636 | Discussion on signalling based feeder link switch | CATT |
| R3-224637 | Support of signalling based feeder link switch-over in XnAP | CATT |
| R3-224863 | Discussion on enhancements for feeder link switch over | Samsung |
| R3-225023 | CB: # NTN1_Mobility - Summary of email discussion | Thales - moderator |
| R3-225076 | CB: # NTN1_Mobility - Summary of email discussion | Thales - moderator |
| 17.3 | Network verified UE location | |
| R3-224234 | Network verified UE location aspects | THALES |
| R3-224384 | Discussion on the network verified UE location | Nokia, Nokia Shanghai Bell |
| R3-224578 | Initial Observations on Network Verified UE Location | Ericsson LM |
| R3-224595 | UE location verification | Huawei |
| R3-224623 | Initial consideration on Network verified UE location for NR NTN | ZTE |
| R3-224624 | Cause value on Network verified UE location for NR NTN | ZTE |
| R3-224635 | Discussion on UE location verification for NR NTN | CATT |
| R3-225024 | CB: # NTN2_UELocation - Summary of email discussion | Nokia - moderator |
| 18.1 | General | |
| R3-224625 | Work Plan on IoT NTN Ehancements in Rel-18 | ZTE, MediaTek |
| 18.2 | Support discontinuous coverage | |
| R3-224385 | Discussion on the support for discontinuous coverage | Nokia, Nokia Shanghai Bell |
| R3-224386 | Support for IOT NTN enhancements | Nokia, Nokia Shanghai Bell |
| R3-224575 | Support for Discontinuous Coverage in IoT NTN | Ericsson LM |
| R3-224591 | Discussion on power saving enhancements regarding discontinuous coverage | Huawei |
| R3-224596 | Mobility management enhancements for discontinuous coverage | Huawei |
| R3-224643 | Discussion on Discontinuous Coverage | CATT |
| R3-224708 | Initial consideration on mobility management enhancements for discontinuous coverage | ZTE |
| R3-224709 | Initial consideration on power saving enhancements for discontinuous coverage | ZTE |
| R3-225025 | CB: # IoTNTN_Coverage - Summary of email discussion | ZTE - moderator |
| 21.1 | General | |
| R3-224373 | TR skeleton for Resiliency of gNB-CU-CP | NTT DOCOMO, INC. |
| R3-224582 | Work plan for Resiliency of gNB-CU-CP SI | NTT DOCOMO, INC. |
| R3-225116 | TR 38.879-001_resiliency of gNB-CU-CP SI | NTT DOCOMO, INC. |
| R3-225156 | TR 38.879-001_resiliency of gNB-CU-CP SI | NTT DOCOMO, INC. |
| R3-225212 | TR 38.879-010_resiliency of gNB-CU-CP SI | NTT DOCOMO, INC. |
| R3-225251 | TR 38.879-011_resiliency of gNB-CU-CP SI | NTT DOCOMO, INC. |
| 21.2 | Failure Scenarios associated with the gNB-CU-CP | |
| R3-224280 | Discussion on Failure Scenarios associated with gNB-CU-CP | Nokia, Nokia Shanghai Bell |
| R3-224281 | Text Proposal for gNB-CU-CP Failure Scenarios | Nokia, Nokia Shanghai Bell |
| R3-224302 | Discussion of gNB-CU-CP resiliency scenario | NEC |
| R3-224303 | TP for gNB-CU-CP resiliency scenario | NEC |
| R3-224324 | Discussion on failure scenarios associated with the gNB-CU-CP | Deutsche Telekom AG |
| R3-224369 | Work plan for Resiliency of gNB-CU-CP SI | NTT DOCOMO, INC. |
| R3-224576 | gNB-CU-CP Failure Case for Resiliency Study | Ericsson LM |
| R3-224577 | Final Considerations and Conclusions on gNB-CU-CP Resiliency | Ericsson LM |
| R3-224626 | Initial consideration on resiliency of gNB-CU-CP | ZTE |
| R3-224627 | TP to draft TR for resiliency of gNB-CU-CP | ZTE |
| R3-224754 | (TP for FS_gNB_CU_CP_resiliency for TR 38.xxx) Local Redundancy of Logical CU-CP | Samsung |
| R3-224787 | TP for TR enhancements for resiliency of gNB-CU | NTT DOCOMO INC. |
| R3-224897 | Discussions on enhancements for resiliency of gNB-CU-CP | Huawei |
| R3-224898 | Tentative TP for FS_gNB_CU_CP_resiliency on resiliency of gNB-CU-CP | Huawei |
| R3-225026 | CB: # CPResiliency_FailureCase - Summary of email discussion | NTT Docomo - moderator |
| 22.1 | General | |
| R3-224926 | Work plan for NR network-controlled repeaters | ZTE |
| 22.2 | Support Network-Controlled Repeater Management | |
| R3-224241 | RAN3 Aspects of Network-Controlled Repeater | Qualcomm Inc. |
| R3-224387 | Discussion on Identification and authorization of Network Controlled Repeater | Nokia, Nokia Shanghai Bell |
| R3-224388 | (TP for TR38.867) Update to Identification and authorization of Network Controlled Repeater | Nokia, Nokia Shanghai Bell |
| R3-224507 | RAN3 Aspects of Network-Controlled Repeater | Qualcomm Inc. |
| R3-224567 | NCR Identification and Authorization | Ericsson LM |
| R3-224568 | NCR Study - Proposed Conclusions | Ericsson LM |
| R3-224632 | Discussion on NCR Identification and Authorization | CATT |
| R3-224633 | (TP for TR 38.867) Support of NCR management | CATT |
| R3-224662 | Discussion on NCR identification and authorization | Huawei |
| R3-224663 | (TP to TR 38.867) NR network-controlled repeater identification and authorization | Huawei |
| R3-224755 | (TP for FS_NR_NetCon_Repeater for TR 38.8xx) Authorization for Network Controlled Repeater | Samsung |
| R3-224785 | Identification and Authorization of Network-Controlled Repeater | Intel Corporation |
| R3-224877 | Discussion on NCR identification and authorization | ZTE Corporation |
| R3-224878 | Draft TP to TR 38867 on NCR identification and authorization | ZTE Corporation |
| R3-224917 | Discussion on the network-controlled repeater management | CMCC |
| R3-224927 | On Identification and authorization of Network-Controlled Repeater | China Telecom |
| R3-224953 | TP to TR 38.867 | CMCC |
| R3-224979 | Draft TP to TR 38867 on NCR identification and authorization | ZTE Corporation |
| R3-225027 | CB: # NCR_Solutions - Summary of email discussion | ZTE - moderator |
| R3-225080 | CB: # NCR_Solutions - Summary of email discussion | ZTE - moderator |
| R3-225089 | LS on NCR Solutions | ZTE |
| R3-225106 | pCR for NCR TR 38.867 | ZTE Corporation |
| R3-225146 | LS on NCR identification and authorization | ZTE |
| R3-225215 | pCR for NCR TR 38.867 | ZTE Corporation |
| R3-225216 | LS on NCR Solutions | ZTE |
| R3-225217 | LS on NCR identification and authorization | ZTE |
| R3-225252 | pCR for NCR TR 38.867 | ZTE Corporation |
| R3-225253 | LS on NCR Solutions | ZTE |
| R3-225254 | LS on NCR identification and authorization | ZTE |
| 23.1 | General | |
| R3-224530 | Study on Rel-18 NR Sidelink Positioning | Ericsson |
| R3-224628 | Work Plan for Study Item on Expanded and Improved NR Positioning | CATT, Intel Corporation, Ericsson |
| R3-224629 | TR 38.859 skeleton info | CATT, Intel Corporation, Ericsson |
| 23.2 | Support Enhancements on NR Positioning | |
| R3-224513 | Potential RAN3 impacts of NR carrier phase positioning | Nokia, Nokia Shanghai Bell |
| R3-224514 | Potential RAN3 impacts of positioning support for RedCap UEs | Nokia, Nokia Shanghai Bell |
| R3-224533 | Discussion on Carrier Phase Positioning | Ericsson |
| R3-224630 | Discussion on SL Positioning Architecture and Signaling Procedures | CATT |
| R3-224631 | Discussion on LPHAP and inactive positioning | CATT |
| R3-224701 | Discussion on positioning enhancement | Huawei |
| R3-224702 | Discussion on sidelink positioning | Huawei |
| R3-224765 | Discussion on sidelink positioning | Xiaomi |
| R3-224766 | Discussion on other potential RAN3 impact | Xiaomi |
| R3-224799 | Discussion on service authorization for sidelink positioning to NG-RAN | ZTE |
| R3-224833 | Initial discussion on sidelink positioning | Samsung |
| R3-224916 | Initial consideration on Sidelink positioning | CMCC |
| R3-224956 | Consideration on sidelink positioning | ZTE |
| R3-224982 | Discussion on other potential RAN3 impact | Beijing Xiaomi Mobile Software |
| R3-225033 | CB: # Positioing_PosEnh - Summary of email discussion | Ericsson - moderator |
| 24.1 | General | |
| R3-224731 | Work plan for NR network energy savings | Huawei |
| R3-224732 | TR 38.864 skeleton for NR network energy savings SI | Huawei |
| R3-225090 | RAN3 aspects of NR network energy savings | Huawei |
| R3-225141 | Draft LS on skeleton of TR 38.864 for NR network energy savings | Huawei |
| R3-225203 | LS on skeleton of TR 38.864 for NR network energy savings | Huawei |
| 24.2 | Support Network Energy Savings | |
| R3-224358 | Discussion on other energy saving techniques | Huawei |
| R3-224464 | Initial discussion on RAN3 aspects of energy saving study | Nokia, Nokia Shanghai Bell |
| R3-224465 | Minimum activation time and probing | Nokia, Nokia Shanghai Bell |
| R3-224526 | Discussion on Network Energy Saving SI | Ericsson |
| R3-224528 | Text Proposal to Network Energy Saving SI | Ericsson |
| R3-224614 | Information exchange over network interfaces for network energy savings | Qualcomm Incorporated |
| R3-224653 | Discussion on NR Network Energy Saving Scenarios and Technologies | CATT |
| R3-224654 | [Draft] LS on supported scenarios for Network Energy Saving | CATT |
| R3-224733 | Time-domain network energy saving techniques | Huawei |
| R3-224939 | Initial consideration on Network Energy Saving | ZTE |
| R3-224940 | TP for NW energy saving for 38.864 | ZTE |
| R3-225028 | CB: # NetworkES_Scenarios - Summary of email discussion | Huawei - moderator |